On Mon 08 Sep 2014 at 13:44:28 -0400, Toby Karyadi wrote: > Say, if I have the following: > - a path a/b/c/d > - a/b/c/d is a mount point for some filesystem > - an alternate path alt-hier/c, which is a null mount for a/b/c > > Then, listing alt-hier/c/d won't show the content of the filesystem mounted > on a/b/c/d. This is surprising, since I thought that I'd see the content of > a/b/c/d. Is this a bug, or my misunderstanding of how the nullfs is supposed > to work? I also tried this on FreeBSD 7.1 and got the same behavior; hmmpfh. I believe that is a general effect. You'd see it with NFS too: if you export a/b/c to some client, it will not see whatever the server has mounted on a/b/c/d. You can always do an extra null mount on alt-hier/c/d, which is the same solution as for NFS. The reasoning is, I think, that a/b/c/d is a different file system from a/b/c, and hence it is not included in the nfs export or null re-mount (which is also a file system export of a kind). -Olaf. -- ___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for \X/ rhialto/at/xs4all.nl -- 'this bath is too hot.'
Attachment:
pgpC8fkGGef8Z.pgp
Description: PGP signature