From owner-freebsd-current@FreeBSD.ORG Thu Nov 13 01:27:02 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53AC7106564A; Thu, 13 Nov 2008 01:27:02 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 188C08FC17; Thu, 13 Nov 2008 01:27:02 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id mAD1R1aJ027392; Wed, 12 Nov 2008 17:27:01 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id mAD1R1H6027391; Wed, 12 Nov 2008 17:27:01 -0800 (PST) (envelope-from sgk) Date: Wed, 12 Nov 2008 17:27:01 -0800 From: Steve Kargl To: Brooks Davis Message-ID: <20081113012701.GA27354@troutmask.apl.washington.edu> References: <20081112235903.GA19865@troutmask.apl.washington.edu> <20081113011506.GA6719@lor.one-eyed-alien.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113011506.GA6719@lor.one-eyed-alien.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: GEOM hangover disables NFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 01:27:02 -0000 On Wed, Nov 12, 2008 at 07:15:06PM -0600, Brooks Davis wrote: > On Wed, Nov 12, 2008 at 03:59:03PM -0800, Steve Kargl wrote: > > On three nodes in my cluster (nodes n17, n18, and n19), I had > > GEOM use /dev/ad4s1e for tests with gmirror and ggated/ggatec. > > I found that GEOM was insufficient for my needs and decided > > to return the 3 partitions to NFS-exported partitions. It seems > > that once GEOM touches a partition, the partition can no longer > > be used by NFS. > > (snip) > > So, how does one exorcise GEOM from /dev/ad4s1e? > > All disks and partitions are always represented as GEOM devices. This is > the only way to access storage so I'm pretty sure you don't actually > want to get rid of GEOM. :) > > The output of "sysctl -b kern.geom.conftxt" would show if there were > bits that were being picked up by a stray geom consumer. A dmesg from > the problem nodes might also be helpful in determining what's wrong. > The best guess would be left over state, probably at the end of the > volumes. If local access to the file system actually works, NFS really > shouldn't care what's been done to the disk below the file system. > Andrzej Tobola pointed me to the NFS_LEGACYRPC kernel option. Seems I chose a bad time to experiment with gmirror and ggated/ggatec in that my fallback plan to plain old NFS had an unforeseen (by me) bug. -- Steve