GEOM hangover disables NFS
sgk at troutmask.apl.washington.edu
Wed Nov 12 17:27:02 PST 2008
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.
> > 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.
More information about the freebsd-current