From: matt <matt@angalon.org>
To: autofs@linux.kernel.org
Subject: Understanding direct mounts & ghosting
Date: Wed, 10 Mar 2004 22:44:45 -0600 [thread overview]
Message-ID: <404FEEBD.70507@angalon.org> (raw)
I am attempting to use direct mounts with autofs4 and either I'm doing
something wrong or I'm expecting the wrong behaviour. Here's my
situation. I installed SuSE 9.0 and then downloaded and built
autofs-4.1.0 and autofs4-2.4 kernel module. I installed both and added
the alias line in modules.conf, and when I do 'lsmod' I see 'autofs4' as
the autofs module so I think I've got the kernel part right.
The reason I am trying to get direct mounts to work is so that I can
automount /usr/local from my fileserver, however if I put the line:
/usr/local server:/usr/local
into my auto.direct file, then all of /usr goes away (except
/usr/local). So for testing purposed I changed things to use /mnt. Now
my auto.master includes the line:
/- auto.direct
and the auto.direct file contains:
/mnt/local voorg:/usr/local
Once I start the automounter I see the following as part of the output
of the mount command:
automount(pid27283) on /mnt type autofs
(rw,fd=5,pgrp=27279,minproto=2,maxproto=4)
and my test directory (/mnt/local.orig) is no longer visible. If I then
cd to /mnt/local the mount command shows:
automount(pid27283) on /mnt type autofs
(rw,fd=5,pgrp=27279,minproto=2,maxproto=4)
voorg:/usr/local on /mnt/local type nfs (rw,addr=192.168.222.5)
So the automount does appear to be working; but not as I expect a direct
mount to work based on my experience with Solaris (and HPUX). My
expecataion is that I should see /mnt/local as the automount point (i.e.
"automount(pid27238) on /mnt/local type autofs ...") instead of /mnt.
Is this the expected behavior or am I missing something?
With regards to ghosting, I have another map (auto.nfs) that's mounted
on /nfs and, as I understand ghosting, I should be able to do:
ls /nfs
and see a list of mountable directories (i.e. the contents of the
auto.nfs map) as a result. I don't. All I see is . and .. (presuming
of coure that I haven't cd'd to any of the mount-points).
Anything you can offer to help me understand what's happening would be
greatly appreciated. And if I can provide additional info about my
setup, please let me know.
Thanks much,
Matt
next reply other threads:[~2004-03-11 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 4:44 matt [this message]
2004-03-12 1:26 ` Understanding direct mounts & ghosting 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=404FEEBD.70507@angalon.org \
--to=matt@angalon.org \
--cc=autofs@linux.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.