From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: automount doesn't "follow" bind mounts
Date: 20 Aug 2002 14:35:26 -0700 [thread overview]
Message-ID: <ajucmu$1qd$1@cesium.transmeta.com> (raw)
In-Reply-To: ajuahu$hf$1@cesium.transmeta.com
Followup to: <ajuahu$hf$1@cesium.transmeta.com>
By author: "H. Peter Anvin" <hpa@zytor.com>
In newsgroup: linux.dev.kernel
>
> Followup to: <Pine.LNX.4.44.0208201752430.23681-100000@r2-pc.dcs.qmul.ac.uk>
> By author: Matt Bernstein <mb/lkml@dcs.qmul.ac.uk>
> In newsgroup: linux.dev.kernel
> >
> > I tried to subscribe to the autofs list, but majordomo isn't replying to
> > me! I think this is a problem in the automount daemon rather than the
> > kernel autofs code itself.
> >
> > I'm trying to automount our home dirs as
> > /homes/$USERNAME
> > which should bind mount to
> > :/home/$SERVER/$HOMENAME/$USERNAME
> > which should bind mount to
> > :/home/$SERVER/$VOLUME/$PATH/$USERNAME
> > which (phew!) will be an NFS mount to
> > $SERVER:/$VOLUME/$PATH/$USERNAME
> >
> > The idea is that:
> > (1) `/bin/pwd` = "/homes/$USERNAME"
> > (2) when you run "quota" it'll only report for $SERVER:/$VOLUME
> >
> > Now.. this all works perfectly if before looking at /homes/$USERNAME you
> > look at firstly /home/$SERVER/$VOLUME/$PATH/$USERNAME and then secondly
> > /home/$SERVER/$HOMENAME/$USERNAME, because the bind mounts have something
> > to bind to. Of course you shouldn't need to know the middle bits, but you
> > could look them up. Currently the binds mount fail and automount drops in
> > symlinks; this satisfies (2) above, but unfortunately not (1).
> >
> > I hope someone can make sense of this. Is it different in autofs4?
> >
>
> This is unfortunately nearly impossible to solve. It's a known bug,
> but it's questionable if anything can be done about it.
>
> For right now, autofs cannot bind-mount to a mount from the same
> automount point (the problem is with the double-use of /home/$SERVER
> in your case.)
>
Actually, if you're using autofs v3, which it sounds like you're
doing, it's even more broken, since autofs v3 doesn't support
multilevel mounts.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-08-20 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 17:10 automount doesn't "follow" bind mounts Matt Bernstein
2002-08-20 20:58 ` H. Peter Anvin
2002-08-20 21:35 ` H. Peter Anvin [this message]
2002-08-20 22:09 ` Benjamin LaHaise
2002-08-20 22:18 ` H. Peter Anvin
2002-08-20 22:20 ` Benjamin LaHaise
2002-08-20 22:21 ` H. Peter Anvin
2002-08-21 0:33 ` stoffel
2002-08-21 0:35 ` H. Peter Anvin
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='ajucmu$1qd$1@cesium.transmeta.com' \
--to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.