Description of problem: After replacing a brick in disperse volume, shd does not start healing the newly added brick (added by "replace-brick" command). heal info would not display any entries to be healed which is incorrect information. Full heal is required to be invoked manually to write data on newly added brick. Version-Release number of selected component (if applicable): [root@aspandey glusterfs]# gluster --version glusterfs 3.8dev built on Aug 17 2015 13:13:53 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. How reproducible: 100% Steps to Reproduce: 1 - Create a 4+2 disperse volume 2 - Fuse mount this volume and write some data (dir/files/links) on mount point 3 - Replace a brick for this volume on server side. 4 - Execute "gluster v heal <vol name> info" - It displays 0 as entry 5 - Check newly added brick location - No data is written on this brick. Actual results: Healing of data on new brick is not getting started as soon as we replace a brick. Expected results: Healing of data on new brick should be started as soon as we replace a brick.
REVIEW: http://review.gluster.org/13353 (cluster/ec: Automate heal for replace brick) posted (#1) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/13353 (cluster/ec: Automate heal for replace brick) posted (#2) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/13353 (cluster/ec: Automate heal for replace brick) posted (#3) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/13353 (cluster/ec: Automate heal for replace brick) posted (#4) for review on master by Ashish Pandey (aspandey)
COMMIT: http://review.gluster.org/13353 committed in master by Xavier Hernandez (xhernandez) ------ commit 12fbcd22d80be9cdd7e60341a173741d1d00f711 Author: Ashish Pandey <aspandey> Date: Thu Feb 4 12:07:36 2016 +0530 cluster/ec: Automate heal for replace brick Problem: After a replace brick command, newly added brick does not contain data which existed on old brick. Solution: Do getxattr after initialization of all the bricks. This will trigger heal for brick root as soon as it finds the version mismatch on newly added brick. Removing tests from ec-new-entry.t which were required to simulate automation of heal after replace brick. Change-Id: I08e3dfa565374097f6c08856325ea77727437e11 BUG: 1304686 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: http://review.gluster.org/13353 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user