[Bugs] [Bug 1425703] New: [Disperse] Metadata version is not healing when a brick is down

[bugzilla at redhat.com]

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

            Bug ID: 1425703
           Summary: [Disperse] Metadata version is not healing when a
                    brick is down
           Product: GlusterFS
           Version: mainline
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: aspandey at redhat.com
                CC: bugs at gluster.org



Description of problem:

When a brick-1 is down and we create a file on mount point, index entries will
be created. Now when this brick is UP and the other brick goes down, heal
starts on the bric-1 and it heal all the data and also its version. However on
the metadata version on the brick-1 is not getting healed and remains 0




Version-Release number of selected component (if applicable):

[root at apandey glusterfs]# gluster --version
glusterfs 3.11dev
Repository revision: git://git.gluster.org/glusterfs.git
Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
It is licensed to you under your choice of the GNU Lesser
General Public License, version 3 or any later version (LGPLv3
or later), or the GNU General Public License, version 2 (GPLv2),
in all cases as published by the Free Software Foundation

How reproducible:
100%

Steps to Reproduce:
1. Create a (4+2) volume and mount it.
2. Kill a brick, brick-1, and create 10 files on mount point.
3. Start the volume using force and kill other brick, brick-2, immediately.     
4. start index heal and give enough time to heal.
5. At this point all the files on brick-1 should have correct version and size
as with other 4 UP bricks and all the files should be healed.

6. Check trusted.ec.{version,size}, it should be same on all the 5 up bricks

Actual results:
Step 6 shows metadata version on brick-1 has not been healed.

Expected results:
Step 6 should show metadata version on brick-1 has been healed and similar to
other 4 good UP bricks.

Additional info:

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