Date: Tue, 14 Sep 2004 16:25:33 +0800 (WST)
From: Ian Kent <raven@themaw.net>
To: Mitch Sako <msako@cadence.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: autofs4 /net /proc/mounts problem
In-Reply-To: <6.1.2.0.2.20040913092535.0d1d5aa0@mailhub>
Message-ID: <Pine.LNX.4.58.0409141623440.27621@wombat.indigo.net.au>
References: <6.1.2.0.2.20040913092535.0d1d5aa0@mailhub>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1499
Lines: 42

On Mon, 13 Sep 2004, Mitch Sako wrote:

> I?m seeing the following situation occur with 2.4.23 up through 2.4.27 and 
> autofs 4.1.3 using /net access with a generic /etc/auto.net.  I tried 
> 'nonstrict' and 'nosymlink' in /etc/auto.net but that resulted in the 
> mounts not working.
> 
> NFS Server foo has virtual nested exports:
> / on /dev/sda1
> /bar on /dev/sdb1 (for example)
> 
> cd /net/foo/bar mounts both / and /bar which it finds from ?showmount ?e?
> 
> df shows foo:/ and foo:/bar mounted
> 
> /proc/mounts shows both, also.
> 
> I?m guessing what?s happening next is autofs4 tries to umount foo:/ before 
> foo:/bar which yields a busy condition for foo:/, even though it?s not 
> because foo:/bar is mounted above foo:/ on the client.
> 
> /proc/mounts starts filling up with foo:/bar entries at this point and 
> fills up the mount table.
> 
> If I bring down the automount process, manually go through and umount all 
> of the foo:/bar entries in /proc/mounts, clean up anything in /etc/mtab and 
> then restart the automounter, everything seems to be OK.  Obviously, this 
> is not acceptable.
> 
> Any ideas?

Are you using a kernel with the latest autofs4 patch?

btw the place for these questions is the autofs mailing list.

Ian

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/