[Bugs] [Bug 1804591] New: Heal pending on volume, even after all the bricks are up

bugzilla at redhat.com bugzilla at redhat.com
Wed Feb 19 08:34:25 UTC 2020


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

            Bug ID: 1804591
           Summary: Heal pending on volume, even after all the bricks are
                    up
           Product: GlusterFS
           Version: 7
          Hardware: x86_64
                OS: Linux
            Status: NEW
         Component: replicate
          Keywords: Triaged
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org, mwaykole at redhat.com,
                    ravishankar at redhat.com, sasundar at redhat.com
        Depends On: 1792821, 1801624
  Target Milestone: ---
    Classification: Community



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

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

ew on master by Ravishankar N

--- Additional comment from SATHEESARAN on 2020-02-11 14:58:47 UTC ---

Steps to reproduce:

1. Create replica 3 volume
2. Enable 'granular-entry-heal' on the volume
# gluster volume heal <vol> granular-entry-heal enable
3. Fuse mount the volume
4. Create a file 'f1' on the fuse mount
5. Kill one of the brick say 'b2'
6. Now remove the file 'f1' and create a new file 'f1'
7. Trigger heal, even before bringing up the down brick
# gluster volume heal <vol>
8. Bring the brick up
9. Check for heal info

--- Additional comment from Worker Ant on 2020-02-18 09:12:11 UTC ---

REVIEW: https://review.gluster.org/24109 (afr: prevent spurious entry heals
leading to gfid split-brain) merged (#8) on master by Ravishankar N


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1792821
[Bug 1792821] Heal pending on brick post upgrading from RHV 4.2.8 or RHV 4.3.7
to RHV 4.3.8
https://bugzilla.redhat.com/show_bug.cgi?id=1801624
[Bug 1801624] Heal pending on volume, even after all the bricks are up
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list