[Bugs] [Bug 1312816] gfid-reset of a directory in distributed replicate volume doesn't set gfid on 2nd till last subvolumes
bugzilla at redhat.com
bugzilla at redhat.com
Wed Mar 2 08:55:01 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1312816
--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13545 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com)
------
commit 9b022c3a3f2f774904b5b458ae065425b46cc15d
Author: Pranith Kumar K <pkarampu at redhat.com>
Date: Sat Feb 27 23:08:06 2016 +0530
cluster/afr: Don't delete gfid-req from lookup request
Problem:
Afr does dict_ref of the xattr_req that comes to it and deletes "gfid-req"
key.
Dht uses same dict to send lookup to other subvolumes. So in case of
directories and more than 1 dht subvolumes, second subvolume till the last
subvolume won't get a lookup request with "gfid-req". So gfid reset never
happens on the directories in distributed replicate subvolume for 2nd till
last
subvolumes.
Fix:
Make a copy of lookup xattr request.
Also fixed replies_wipe possibly resetting gfid to NULL gfid
BUG: 1312816
Change-Id: Ic16260e5a4664837d069c1dc05b9e96ca05bda88
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
Reviewed-on: http://review.gluster.org/13545
Smoke: Gluster Build System <jenkins at build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Krutika Dhananjay <kdhananj at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=iGBatXJK95&a=cc_unsubscribe
More information about the Bugs
mailing list