Description of problem: While reading code I observed that metadata sync is happening outside metadata locks, this can lead to inconsistencies if new metadata operations are happening at the same time. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/8514 (cluster/afr: Perform metadata sync inside metadata locks) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/8514 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit bc38d564663a64072ca508da12a8b4b6d48995e9 Author: Pranith Kumar K <pkarampu> Date: Thu Aug 21 17:30:10 2014 +0530 cluster/afr: Perform metadata sync inside metadata locks Change-Id: Ie55b3d37cacbdad74a3f63c3b0f025b0ffd0104a BUG: 1132461 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/8514 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