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

[bugzilla at redhat.com]

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

            Bug ID: 1265077
           Summary: Start self-heal and display correct heal info after
                    replace brick
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: disperse
          Assignee: aspandey at redhat.com
          Reporter: pkarampu at redhat.com
        QA Contact: byarlaga at redhat.com
                CC: aspandey at redhat.com, bugs at gluster.org,
                    byarlaga at redhat.com, gluster-bugs at redhat.com,
                    pkarampu at redhat.com, xhernandez at datalab.es
        Depends On: 1254121
            Blocks: 1258313
             Group: redhat



+++ This bug was initially created as a clone of Bug #1254121 +++

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:

--- Additional comment from Anand Avati on 2015-08-17 07:22:24 EDT ---

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 at redhat.com)

--- Additional comment from Anand Avati on 2015-08-30 14:36:31 EDT ---

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 at redhat.com)

--- Additional comment from Anand Avati on 2015-08-31 03:51:25 EDT ---

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 at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1254121
[Bug 1254121] Start self-heal and display correct heal info after replace
brick
https://bugzilla.redhat.com/show_bug.cgi?id=1258313
[Bug 1258313] Start self-heal and display correct heal info after replace
brick
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=m1UhXvooAU&a=cc_unsubscribe