REVIEW: http://review.gluster.org/12361 (cluster/ec : Remove index entries if file/dir does not exist) posted (#1) for review on release-3.7 by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/12361 (cluster/ec : Remove index entries if file/dir does not exist) posted (#2) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/12361 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit 9a14852e95880b08f9209384032e7e5413b493b2 Author: Ashish Pandey <aspandey> Date: Tue Oct 13 23:25:59 2015 +0530 cluster/ec : Remove index entries if file/dir does not exist Backport of http://review.gluster.org/12353 Problem: During write and rebalance if a brick is down, index entries will be created. If the same file gets migrated to other subvol by rebalance process, these index entries will remain in index directory. During heal, these indices should be removed when we get ENOENT or ESTALE for a index. Solution: Capture correct errno and take appropriate action to purge these indices. Change-Id: I1aad8b99e4df2e139648e3bf971e4cb1c4b38699 Bug: 1271967 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: http://review.gluster.org/12361 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
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.6, please open a new bug report. glusterfs-3.7.6 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://www.gluster.org/pipermail/gluster-users/2015-November/024359.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user