Bug 1254121 - Start self-heal and display correct heal info after replace brick
Summary: Start self-heal and display correct heal info after replace brick
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ashish Pandey
QA Contact: Bhaskarakiran
URL:
Whiteboard:
Depends On:
Blocks: 1258313 1265077 1278284 1304686 1305755
TreeView+ depends on / blocked
 
Reported: 2015-08-17 08:22 UTC by Ashish Pandey
Modified: 2016-11-23 23:13 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1258313 1265077 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:32:25 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Ashish Pandey 2015-08-17 08:22:24 UTC
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.

Additional info:

Comment 1 Anand Avati 2015-08-17 11:22:24 UTC
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 (aspandey@redhat.com)

Comment 2 Anand Avati 2015-08-30 18:36:31 UTC
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 (pkarampu@redhat.com)

Comment 3 Anand Avati 2015-08-31 07:51:25 UTC
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 (vbellur@redhat.com)

Comment 4 Niels de Vos 2016-06-16 13:32:25 UTC
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


Note You need to log in before you can comment on or make changes to this bug.