Bug 1107933
| Summary: | nfs: subdir-suthentication: Failed to resolve and create inode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> | ||||
| Component: | gluster-nfs | Assignee: | Niels de Vos <ndevos> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rhgs-3.0 | CC: | mzywusko | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | glusterfs-server-3.4.0.59rhs-1.el6rhs.x86_64 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-10-23 15:55:05 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: | |||||||
| Attachments: |
|
||||||
This is not reproducible with glusterfs-server-3.4.0.59rhs-1.el6rhs.x86_64 anymore. Following the steps in comment #0 does not result in the error message. Please re-open if this problem is still happening in a current version. |
Created attachment 907477 [details] server nfs.log Description of problem: Tried to mount a subdir on client, after providing the required authentication. The mount command throws error, [2014-06-11 03:38:50.353145] E [mount3.c:888:__mnt3_resolve_export_subdir_comp] 0-nfs-mount: Failed to resolve and create inode: parent gfid 00000000-0000-0000-0000-000000000000, entry 999 although the mount is successful Version-Release number of selected component (if applicable): glusterfs-3.6.0.14-1.el6rhs.x86_64 How reproducible: seen several times Steps to Reproduce: 1. create a new 6x2 volume, start it 2. mount over nfs 3. create some directories in this volume. 4. set nfs.export-dirs off 5. provide authentication to a client for a certain directory to allow the client to let it mount the directory. for authentication use the command nfs.export-dir 6. mount the directory on the client. Actual results: mount command, [root@rhel6 nfs-test-dir]# mount | grep nfs-test-dir 10.70.37.215:/dist-rep1/4rename/999 on /mnt/nfs-test-dir type nfs (rw,vers=3,addr=10.70.37.215) nfs.log, [2014-06-11 03:38:50.353145] E [mount3.c:888:__mnt3_resolve_export_subdir_comp] 0-nfs-mount: Failed to resolve and create inode: parent gfid 00000000-0000-0000-0000-000000000000, entry 999 This issue is a problem as it throws error with a zero gfid. Expected results: there should not be any error of this kind. Additional info: subsequent umount and mount does throw the error