Description of problem: Symlink mount fails for nfs-ganesha volume Version-Release number of selected component (if applicable): nfs-ganesha-gluster-2.2.0-3.el6rhs.x86_64 glusterfs-3.7.1-7.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a ganesha volume say nfsvol and enable ganesha on it. 2. mount volume nfsvol at /mnt/nfsvol 3. mkdir /mnt/nfsvol/subdir 4. create symlink ln -s /mnt/nfsvol/subdir /mnt/nfsvol/symlink-subdir umount 5. now mount using symlink volname/symlink-subdir - it fails [root@vm8 ~]# mount -t nfs -o vers=3 10.70.46.59:/testvol/symlink-subdir /mnt/nfs1436550075.6 mount.nfs: an incorrect mount option was specified Actual results: Symlink mount gives an error Expected results: Should be able to do a symlink mount Additional info:
NFSv4 Mount of symlink works but there seem to be an issue with only NFSv3 mount. Investigating the same. [root@skoduri export1]# mount -t nfs -o vers=3 192.168.122.205:/vol1/dir1_link /tmp/mnt mount.nfs: an incorrect mount option was specified [root@skoduri export1]# mount -t nfs -o vers=4 192.168.122.205:/vol1/dir1_link /tmp/mnt [root@skoduri export1]#
nfs-ganesha doesn't resolve symlinks during mount. NFSv4 clients seem to be resolving those symlink filehandle but that is not the case with NFSv3. Based on the discussions we had within the team (& also as per http://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch06_04.htm), we have agreed that nfs server should resolve the symlinks before returning the filehandle during mount. This needs change in both Gluster and NFS-ganesha source code.
Doc text is edited. Please sign off to be included in Known Issues.
Doc text looks good to me
stretch goal for 3.1.1
Gluster side fix got posted in http://review.gluster.org/#/c/11883/. Ganesha side fix requires this patch to be mergeed
The fix in ganesha has posted in https://review.gerrithub.io/#/c/244043/
Verified on nfs-ganesha-2.2.0-6.el7rhgs.x86_64
Jiffin, Could you review and sign-off the edited doc text.
Needs certain modification to Doc text. Previously , if the mount path for NFSv3 contained symbolic links, then NFSv3 mount failed. With this fix, NFS server resolves the symbolic links in the mount path before sending to client, hence mount will succeed.
Updated the doc text with a minor edit.
Doc text looks good to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1845.html