From: Mitch Sako <msako@cadence.com>
To: linux-kernel@vger.kernel.org
Subject: autofs4 /net /proc/mounts problem
Date: Mon, 13 Sep 2004 09:28:40 -0700 [thread overview]
Message-ID: <6.1.2.0.2.20040913092535.0d1d5aa0@mailhub> (raw)
Im 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.
Im guessing whats happening next is autofs4 tries to umount foo:/ before
foo:/bar which yields a busy condition for foo:/, even though its 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?
next reply other threads:[~2004-09-13 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 16:28 Mitch Sako [this message]
2004-09-14 8:25 ` Ian Kent
2004-09-14 8:29 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6.1.2.0.2.20040913092535.0d1d5aa0@mailhub \
--to=msako@cadence.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®