Bug 763781 (GLUSTER-2049) - files created in the backend are not visible on mount point
Summary: files created in the backend are not visible on mount point
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-2049
Product: GlusterFS
Classification: Community
Component: nfs
Version: 3.1.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Shehjar Tikoo
QA Contact:
URL:
Whiteboard:
: GLUSTER-2125 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-03 07:42 UTC by Krishna Srinivas
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: nfs
Documentation: DNR
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shehjar Tikoo 2010-11-03 04:57:35 UTC 
NFS sets gfids only through the lookup call which means that if a file is seen for the first time throught rdirp request, the file handle will be 0, because a prior lookup wasnt sent on it.

This can happen in situations like:

1. vmstor, which manipulates the backend
2. migration of backend from 3.0 branch.

In 1, because the backends are continuously modified by vmstor's posix, we need to always run with nodirplus mount option at nfs client.

For 2, only to migrate the backend this option is needed. Once the ls -lR to  migrate is complete over the nfs mount,a remount with the readdirp request will work just fine.

Kris will confirm.
Comment 1 Krishna Srinivas 2010-11-03 07:42:55 UTC 
files created directly on the backend are not visible on the mount point, this is because nfs issues readdirp which returns entries with blank gfids and hence lookups are never sent to these entries to apply uuids to the entries.
Comment 2 Shehjar Tikoo 2010-11-09 03:22:39 UTC 
Kris, please re-open if this continues to be a problem with the nordirplus mount option. Thanks.
Comment 3 Shehjar Tikoo 2011-02-22 03:26:49 UTC 
*** Bug 2125 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.