> 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)
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
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/