Michelle Konzack wrote: [Fri Aug 03 2007, 07:57:36AM EDT]
> Which can not work, since /proc must be the /proc of the machine WHICH
> is mounting the nfs-share.
Your statements represent a misreading of the bug. Let's take
a step-by-step approach:
1. The server has /etc/exports:
/foo 10.0.0.0/16(rw,no_root_squash,async,no_subtree_check)
2. The client can see the content of that filesystem, for example:
/foo/bar/baz.txt
3. The server now mounts a directory:
mount /dev/sdb1 /foo/bar
4. Now at this point, the server should see new content on /foo/bar,
but the client should continue to see the underlying content. In
other words, the client can still access /foo/bar/baz.txt
HOWEVER, in some cases at least, the NFS connection is instead hanging
on step 4. The client sends a LOOKUP on /foo/bar and the server never
responds. The client retransmits the LOOKUP indefinitely.
This seems to be easy to demostrate by mounting procfs on /foo/bar,
but I've now seen it using other filesystems.
The only reason I use the chroot example is because it is common to
export a chroot environment as nfs-root. The clients see only the one
filesystem, yes, but the server mounts additional directories so that
it's possible to build and install software more easily in the server
environment.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
