[Bugs] [Bug 1254121] New: Start self-heal and display correct heal info after replace brick

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1254121

            Bug ID: 1254121
           Summary: Start self-heal and display correct heal info after
                    replace brick
           Product: GlusterFS
           Version: mainline
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: aspandey at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



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 at 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:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.