From: "H. Peter Anvin" <hpa@zytor.com>
To: Eric Werme USG <werme@zk3.dec.com>
Cc: autofs@linux.kernel.org, alexander.marx@hp.com
Subject: Re: autofs no_local_binds option (nfs <-> bind mounts)
Date: Tue, 13 Jan 2004 13:04:51 -0800 [thread overview]
Message-ID: <40045D73.4010103@zytor.com> (raw)
In-Reply-To: <200401132042.i0DKgDR0001085265@anw.zk3.dec.com>
Eric Werme USG wrote:
>
> Ah. Back to automount/autofs. I made many fixes to Sun's old automount,
> one of them was to rummage among all the NICs looking to see if the
> FS was really a local mount and provide the appropriate symlink. The
> cluster folks didn't realize I also checked the alias addresses too,
> so I had to add an option to disable that to force a real NFS call.
>
Perhaps I should clarify the algorithm used by autofs: it actually goes
through and creates a socket and connects it to each of the IP addresses
for a server (it uses a UDP socket, so it doesn't actually cause any
network traffic.) Then it queries that socket to see what the local and
remote addresses the kernel chose for the socket. If for any of the
possible addresses <local address == remote address> then the address is
deemed local and autofs will bind-mount. It is thus strictly based on
what the kernel would choose as the local address. If you can force the
local address to be something other than the remote address -- as you
need for relocatability anyway -- then autofs will quite correctly avoid
bind-mounting it.
Mike raised the at least theoretical issue of what about synthetic NFS
servers in userspace and similar issues. I'm not convinced this is an
issue in practice, but we came up with the suggestion of making an
*explicit* -fstype=nfs force NFS mounting regardless. This has the
advantage that it cleans up the daemon somewhat; instead of:
parse_sun
|
mount_nfs
|
mount_bind
one would have:
parse_sun
|
mount_default
/ \
mount_nfs mount_bind
-hpa
next prev parent reply other threads:[~2004-01-13 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 19:58 autofs no_local_binds option (nfs <-> bind mounts) Eric Werme USG
2004-01-13 20:03 ` H. Peter Anvin
2004-01-13 20:23 ` Dylan
2004-01-13 20:25 ` H. Peter Anvin
2004-01-13 20:58 ` Mike Waychison
2004-01-13 21:06 ` H. Peter Anvin
2004-01-13 20:42 ` Eric Werme USG
2004-01-13 20:54 ` H. Peter Anvin
2004-01-13 21:04 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 14:26 MARX,ALEXANDER (HP-Germany,ex1)
2004-01-13 17:14 ` H. Peter Anvin
2004-01-13 17:48 ` Mike Waychison
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=40045D73.4010103@zytor.com \
--to=hpa@zytor.com \
--cc=alexander.marx@hp.com \
--cc=autofs@linux.kernel.org \
--cc=werme@zk3.dec.com \
/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.