Description of problem: find <mnt> | xargs stat from two mounts in parallel leads to mismatching gfids on replicate volume Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. On both the bricks of replicate volume create the same directory hierarchy 2. have two fuse mounts on this volume 3. In parallel execute find <mnt> | xargs stat 4. find fails with Input/output error. If we do getfattr on that file it gives gfid-mismatch. Actual results: Find should succeed and gfid-mismatch should not happen Expected results: Additional info:
REVIEW: http://review.gluster.org/8466 (cluster/afr: Perform gfid heal inside locks) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/8466 (cluster/afr: Perform gfid heal inside locks.) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/8466 (cluster/afr: Perform gfid heal inside locks.) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/8466 (cluster/afr: Perform gfid heal inside locks.) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/8512 (cluster/afr: Perform gfid heal inside locks.) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/8512 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 3b70b160a46b22b77a8ad1897440ec1346795a0f Author: Pranith Kumar K <pkarampu> Date: Wed Aug 13 11:11:17 2014 +0530 cluster/afr: Perform gfid heal inside locks. Problem: Allowing lookup with 'gfid-req' will lead to assigning gfid at posix layer. When two mounts perform lookup in parallel that can lead to both bricks getting different gfids leading to gfid-mismatch/EIO for the lookup. Fix: Perform gfid heal inside lock. BUG: 1129529 Change-Id: I20c6c5e25ee27eeb906bff2f4c8ad0da18d00090 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/8512 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krutika Dhananjay <kdhananj>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user