Date: Thu, 23 Apr 2015 11:16:53 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@FreeBSD.org> To: David Boyd <David.Boyd49@twc.com> Cc: freebsd-current@freebsd.org Subject: Re: AUTOFS and NFS not playing together nicely Message-ID: <20150423091653.GA1607@brick.home> In-Reply-To: <1429477202.29812.38.camel@gemini.bsd1.net> References: <1429477202.29812.38.camel@gemini.bsd1.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 0419T1700, David Boyd wrote: > At the risk of being dubbed insane, here goes: > > On five FreeBSD 10.1-RELEASE-p9 production servers autofs(5) is enabled > and working as advertised. On the same servers nfs v3 clients are also > fat, dumb and happy. > > On a test server where autofs(5) is also enabled and working well, I am > testing nfs v3 (later v4) server. Strange things are happening. > > When nfs mountd(8) is running, the autofs(5) auto-mount (via automountd) > function seems to work, but the autofs(5) auto-unmount (via > autounmountd) never occurs. > > Without nfs mountd(8), when the filesystem /disc is auto-mounted (via > autoumountd), the mount(8) command shows status of (ufs, local, > journaled soft-updates, auto-mounted) for the auto-mounted filesystem > and after the autofs(5) timeout period (600 seconds) the filesystem is > auto-unmounted (via autounmountd). No problem. > > With nfs mountd(8) the mount(8) command shows (ufs, local, journaled > soft-updates). The auto-mounted filesystem is never (a long, long time) > unmounted. Big problem. > > Without nfs mountd(8) running, the mount(8) command "mount -o > automounted /dev/ada0p8 /disc" mounts the filesystem and the mount(8) > command shows (ufs, local, journaled soft-updates, automounted) for the > manually mounted filesystem and after the autofs(5) timeout period (600 > seconds) the filesystem is auto-unmounted even though it was not mounted > automatically. No problem. > > With nfs mountd(8), the mount(8) command "mount -o > automounted /dev/ada0p8 /disc" mounts the filesystem but the mount(8) > command shows (ufs, local, journaled soft-updates) and after the timeout > period (600 seconds) the filesystem is remains mounted. Big problem. > > It appears that nfs mountd(8) is interferring with the mount(8) > command's -o option processing but admittedly that is just a very weak > SWAG. That's an interesting bug. I can reproduce it, but hadn't tracked down the cause just yet. I'll work on that shortly. Thanks for reporting!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150423091653.GA1607>