+++ This bug was initially created as a clone of Bug #1149723 +++ Description of problem: When a file is missing or corrupt on a brick of a dispersed volume, self-heal repairs it, but the modification time is not updated correctly (it contains the time at which self-heal healed the file, not the original modification time of the file). Version-Release number of selected component (if applicable): master How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/8906 (ec: Fix incorrect management of healed bricks) posted (#1) for review on release-3.6 by Xavier Hernandez (xhernandez)
REVIEW: http://review.gluster.org/8906 (ec: Fix incorrect management of healed bricks) posted (#2) for review on release-3.6 by Xavier Hernandez (xhernandez)
REVIEW: http://review.gluster.org/8906 (ec: Fix incorrect management of healed bricks) posted (#3) for review on release-3.6 by Xavier Hernandez (xhernandez)
COMMIT: http://review.gluster.org/8906 committed in release-3.6 by Vijay Bellur (vbellur) ------ commit b2a1be0f7bf5e19b266ee57c3287ee9f9170e2f7 Author: Xavier Hernandez <xhernandez> Date: Mon Oct 6 16:34:58 2014 +0200 ec: Fix incorrect management of healed bricks The final lookup made to restore final file attributes after a self-heal did clear the mask of bad bricks, causing that the final setattr won't modify any brick at all. This caused that some attriutes, specially the modification time of the file didn't get updated properly. Now the mask of healed bricks is saved before doing the last lookup. It's also used to correctly report the repaired bricks. This is a backport of http://review.gluster.org/8905/ Change-Id: Ib94083c9e1b562515dfb54f9574120f1f031dccc BUG: 1149725 Signed-off-by: Xavier Hernandez <xhernandez> Reviewed-on: http://review.gluster.org/8906 Reviewed-by: Dan Lambright <dlambrig> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users