Description of problem: ======================= When we bring down another brick before bringing up a brick which requires healing, the ec version is not updating to lates post the healing of brick1 Version-Release number of selected component (if applicable): ======= 3.8.4-28 How reproducible: ======== always Steps to Reproduce: 1.have a 4+2 ecvol 2.create a dir dir1 and some file say dir1/a{1..10} 3.now bring down b1 and create dir1/b{1..10} 4. now bring down b2 and bring up b1 5. wait for heal to complete,note that heal info will still show as pending as per current ec design it needs all bricks to be up for removing entries 6. check for healing is completed or not from brick background 7. now check the ec version of the sink brick using exattrs The ec version on sink brick is not updating to latest version ##### SINK BRICK ############# [root@dhcp35-45 ~]# getfattr -d -m . -e hex /rhs/brick10/disperse/dir1 getfattr: Removing leading '/' from absolute path names # file: rhs/brick10/disperse/dir1 security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000 trusted.ec.version=0x0000000000000014000000000000000c trusted.gfid=0x764460665cec449fbcd100384374d925 trusted.glusterfs.dht=0x000000010000000000000000ffffffff ####### SOURCE BRICK ########## [root@dhcp35-45 ~]# getfattr -d -m . -e hex /rhs/brick11/disperse/dir1 getfattr: Removing leading '/' from absolute path names # file: rhs/brick11/disperse/dir1 security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000 trusted.ec.dirty=0x00000000000000000000000000000000 trusted.ec.version=0x00000000000000140000000000000016 trusted.gfid=0x764460665cec449fbcd100384374d925 trusted.glusterfs.dht=0x000000010000000000000000ffffffff This problem is gone, once i bring back b2 up
As discussed and agreed upon by all the stake holders, deferring this bug from rhgs-3.3.0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2607