John Cui wrote: > Hi, > When trying share and mount, the behaviors of mount are different when > using the part of the path of exported fs with vers=2,3,4 > On server: > # share /a/b/c > On client: > > # mount server:/a/b /mnt > or > # mount -o vers=4 server:/a/b /mnt > It succeeds, and c is under /mnt. > # nfsstat -m > /mnt from server:/a/b > Flags: > vers=4,proto=tcp,sec=sys,hard,intr,link,symlink,acl,rsize=1048576,wsize=1048576,retrans=5,timeo=600 > Attr cache: acregmin=3,acregmax=60,acdirmin=30,acdirmax=60 > > # mount -o vers=2 server:/a/b /mnt > or > # mount -o vers=3 server:/a/b /mnt > > It will return "Permission denied" > > So is it expected result of pseudo-fs? > > Thanks, > >
Okay, I don't need traces. You are right that NFSv4's pseudo-fs is letting you mount server:/a/b. The only mount call which will work from v2 or v3 is: # mount -o vers=3 ultralord:/a/b/c /mnt A way to check to see that a pseudo-fs is in play is to try the following: On the server: mkdir -p /a/b/c mkdir /a/b/c1 On the client: mount server:/a/b /mnt ls -la /mnt And see if you can see c1 or not.
