From: Ian Kent <raven@themaw.net>
To: Frank Thommen <fthommen@embl.de>
Cc: autofs@linux.kernel.org
Subject: Re: Indirect mounts with map on automounted filesystem and --fstype=autofs
Date: Fri, 19 Feb 2010 11:09:23 +0800 [thread overview]
Message-ID: <4B7E00E3.8090505@themaw.net> (raw)
In-Reply-To: <4B7DCC9A.9030508@embl.de>
On 02/19/2010 07:26 AM, Frank Thommen wrote:
> Hi,
>
> (I'm sure this has already been discussed on this list but somehow I
> seem unable to find the right thread or otherwise an answer on the web...)
>
> I need to automount subdirectories of an automounted filesystem by using
> an indirect map which lies itself on an automounted filesystem:
>
> /base/sub1/ <- mounted via auto.master and indirect map
> /base/sub1/sub2/a <- mounted via indirect a map in /base/sub1
>
> 'sub2' is a "physically" existing directory in /base/sub1
> (server1:/export/sub1, in example below).
>
>
> I managed to do it with the following:
>
>
> /etc/auto.master
> ----------------
> /base file:/etc/auto.base --ghost
>
>
> /etc/auto.base
> --------------
> sub1 / server1:/export/sub1 \
> /sub2 -fstype=autofs file:/main/sub1/my.map
>
>
> /base/sub1/my.map
> ----------------------
> a servera:/export/a
> b serverb:/export/b
> ...
>
>
>
> My two questions are:
>
> a) Is this the right and recommended way to use an indirect map which is
> located on an automounted filesystem or are the better/more
> efficient/faster ways to do it?
These are submounts.
I don't think there's any other way to do this and this is the only
supported way to do nested mounts that I'm aware of.
>
> b) is the -fstype=autofs option an official option that will stay or
> rather an unofficial option that might disappear in the future? The
> manpages don't mention this kind of filesystem
> (autofs-5.0.1-0.rc2.131.el5_4.1 on CentOS 5.4), so I'm unsure about it's
> status.
Ha, I wish I could get rid of support for submounts but that's not going
to happen because they have been available for a long time and quite a
few people need to use them and it's the only supported way to create
nested mounts.
They have been very difficult to get working well in v5 and while there
are probably still problems they seem to be holding up under fairly
heavy usage now.
>
>
> Thank you for any hint or referral to other online documentation.
Yes, the documentation does need some information on multi-mounts and
some reference to submounts. My bad.
Ian
prev parent reply other threads:[~2010-02-19 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 23:26 Indirect mounts with map on automounted filesystem and --fstype=autofs Frank Thommen
2010-02-19 3:09 ` Ian Kent [this message]
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=4B7E00E3.8090505@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=fthommen@embl.de \
/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.