> Frank, Dan. > > Consider the following situation. > > There are 2 configured exports > > exp_id = 10 > Path = /gpfs0/V4 > Pseudo = /gpfs0/V4 > > > exp_id = 20 > Path = /gpfs0/V4/Tom > Pseudo = /gpfs0/V4/Tom > > Client A is allowed to access export ID 20 but is not allowed to access export > ID 10. > > > When trying to mount pseudo /gpfs0/V4/Tom from client A > this always fails with NFS4ERR_NOENT. > > This is because we always walk down exp_id 10 > instead considering exp_id 20. > > The way I understand the spec, this is a supported scenario. > > I don't understand the pseudo-fs concept enough to be able to point > at the issue, therefore ... > > Any thoughts ?
This is NOT a supported scenario for NFSv4... Yea, it happens to work ok for NFS v3... Trying to do this is the equivalent of having the following directory permissions: /home rwx------ /home/ffilz rwxr-xr-x I'm not going to be able to access my home directory... So you could make /gpfs0/v4 read-only to Client A. Or if you REALLY need Client A to not have access, you could have export 20 with: Path /gpfs0/v4/Tom Pseudo /Tom And if you turn on the option that makes v3 mounts use Pseudo instead of Path, client will see consistent view Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
