[Bugs] [Bug 1336320] [Tiering]: Unable to access file(s) from nfs client; gfid mismatch between cold and hot tier entries

bugzilla at redhat.com bugzilla at redhat.com
Mon May 16 07:53:43 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1336320

Nithya Balachandran <nbalacha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Comment #1 is|1                           |0
            private|                            |



--- Comment #2 from Nithya Balachandran <nbalacha at redhat.com> ---
RCA:

I was able to hit this using gdb using the following steps:

1. mount the tier volume using gluster-nfs
2. gdb into the nfs process and set a breakpoint at
tier_create_linkfile_create_cbk
3. On the mount point, create a file using "touch f3"
4. Once the breakpoint is hit, run 'gluster v start <volname> force'. This will
restart the NFS server. The create call is thus aborted after the linkto file
is created but before the data file is.
5. Once the touch command returns, check the gfids of the linkfile and the data
file on the brick. They will be different.


[root at nb-rhs3-srv1 bricks]# getx brick2/hot-*/f3
# file: brick2/hot-3/f3
trusted.gfid=0x4fabbe60d86b402cb064356db35cf798

[root at nb-rhs3-srv1 bricks]# getx brick1/gs1-*/f3
# file: brick1/gs1-3/f3
trusted.gfid=0xbf1f836f07174259b6332759cc58e867
trusted.tier.tier-dht.linkto=0x6773312d686f742d64687400


It looks like the NFS client sends the create call again without a lookup.

This issue also exists in 3.1.2 (reproducible using the same set of steps). So
I am removing the Regression keyword.

--- Additional comment from Nithya Balachandran on 2016-05-12 06:43:20 EDT ---

The same issue exists in dht.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list