From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: vda <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: "David D. Hagood" <David.Hagood@ifrsys.com>,
linux-kernel@vger.kernel.org
Subject: Re: Automount FS re-exported via NFS fails
Date: 13 Nov 2001 17:47:15 +0100 [thread overview]
Message-ID: <shsy9laboto.fsf@charged.uio.no> (raw)
In-Reply-To: <3BF0343C.2080409@ifrsys.com> <01111318193900.00801@nemo>
In-Reply-To: <01111318193900.00801@nemo>
>>>>> " " == vda <vda@port.imtp.ilyichevsk.odessa.ua> writes:
> NFS don't see mountpoints. It's a strange feature but it is
> really done that way. I can mount my /dev/hdc on a non-empty
> dir in NFS exported tree and I see hdc filesystem when browsing
> it locally, but NFS clients still see old dir contents - they
> don't see mounted drive there!
Actually, knfsd can see mountpoints: you just have to explicitly tell
it which mountpoints it is allowed to cross by using the 'nohide'
export option. (man 5 exports)
For instance:
/foo client1
/foo/bar client1(nohide)
Should ensure that client1 can mount /foo, and expect to be able to
see the filesystem on /foo/bar as well...
> I don't know whether it's bug or a feature.
It is an action that is recommended in the RFCs. If you didn't have
this, then you could end up with nasty things happening, for instance,
in the case where the server accidentally re-exports another NFS
partition.
In addition you quickly end up with basic wierdness such as duplicate
inode numbers and the like on the client, since that sees the whole
thing as 1 partition.
Cheers,
Trond
prev parent reply other threads:[~2001-11-13 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 20:42 Automount FS re-exported via NFS fails David D. Hagood
2001-11-13 18:19 ` vda
2001-11-13 16:47 ` Trond Myklebust [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=shsy9laboto.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=David.Hagood@ifrsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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