Red Hat Bugzilla – Bug 1254121
Start self-heal and display correct heal info after replace brick
Last modified: 2016-11-23 18:13:04 EST
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.
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.
Healing of data on new brick is not getting started as soon as we replace a brick.
Healing of data on new brick should be started as soon as we replace a brick.
REVIEW: http://review.gluster.org/11938 (cluster/ec : Self heal all the data on newly added brick in case of "replace-brick command") posted (#1) for review on master by Ashish Pandey (email@example.com)
REVIEW: http://review.gluster.org/11938 (cluster/ec : Mark new entry changelog in entry self-heal) posted (#2) for review on master by Pranith Kumar Karampuri (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/11938 (cluster/ec : Mark new entry changelog in entry self-heal) posted (#3) for review on master by Vijay Bellur (email@example.com)
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.