Bug 1241871
| Summary: | Symlink mount fails for nfs-ganesha volume | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Apeksha <akhakhar> | |
| Component: | nfs-ganesha | Assignee: | Jiffin <jthottan> | |
| Status: | CLOSED ERRATA | QA Contact: | Apeksha <akhakhar> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | rhgs-3.1 | CC: | asriram, asrivast, byarlaga, divya, jthottan, kkeithle, mlawrenc, ndevos, nlevinki, saujain, skoduri, vagarwal | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | RHGS 3.1.1 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | nfs-ganesha-2.2.0-6 | Doc Type: | Bug Fix | |
| 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 the client, hence mount will succeed.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1252410 1257014 (view as bug list) | Environment: | ||
| Last Closed: | 2015-10-05 07:19:43 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1188184, 1216951, 1251815, 1252410, 1256227, 1256616, 1257007, 1257014 | |||
| Deadline: | 2015-08-28 | |||
|
Description
Apeksha
2015-07-10 09:46:42 UTC
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 |