On Wed, 2004-09-01 at 19:16, Kastus wrote:
From man page of exports:
nohide This option is based on the option of the same name provided in IRIX NFS. Normally, if a server exports two filesystems one of which is mounted on the other, then the client will have to mount both filesystems explicitly to get access to them. If it just mounts the parent, it will see an empty directory at the place where the other filesystem is mounted. That filesystem is "hid den".
Setting the nohide option on a filesystem causes it not to be hid den, and an appropriately authorised client will be able to move from the parent to that filesystem without noticing the change.
However, some NFS clients do not cope well with this situation as, for instance, it is then possible for two files in the one apparent filesystem to have the same inode number.
The nohide option is currently only effective on single host exports. It does not work reliably with netgroup, subnet, or wild card exports.
This option can be very useful in some situations, but it should be used with due care, and only after confirming that the client sys tem copes with the situation effectively.
The option can be explicitly disabled with hide.
Regards, -Kastus
Thanks for the reply, I have already tried the nohide option. It didn't work. I'm probably wrong, but to me, the passage: Normally, if a server exports two filesystems one of which is mounted on the other, then the client will have to mount both filesystems explicitly to get access to them. If it just mounts the parent, it will see an empty directory at the place where the other filesystem is mounted. That filesystem is "hid den". refers to if you have folder /x exports as /x and folder /x/y exported as /x/y then the nohide option would work. But that isn't the case here. I only have folder /x exported and the SuSE clients can't follow the tree to /x/y/z where z is a different partition mounted on folder z. Samba shares can follow it and so can MS NFS clients for Windows. On a side note, I have since discovered a discussion from back in '96 talking about how NFSv4 will be able to cross mount points but that version 2 and 3 are not capable of doing it. http://playground.sun.com/pub/nfsv4/nfsv4-wg-archive/1996/0004.html So I guess I will have to recompile my kernel and enable NFSv4 and see if that fixes my problem. K