[Bugs] [Bug 1637802] New: data-self-heal in arbiter volume results in stale locks.

[bugzilla at redhat.com]

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

            Bug ID: 1637802
           Summary: data-self-heal in arbiter volume results in stale
                    locks.
           Product: GlusterFS
           Version: mainline
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org



Description of problem:
commit eb472d82a083883335bc494b87ea175ac43471ff in master introduced a bug
where a data-self-heal on a file in arbiter leaves a stale inodelk behind on
the bricks. Thus any new write to the file from a client can hang

How reproducible:
Always.

Steps to Reproduce:
1. Create 1x (2+1) arbiter, fuse mount it and create a file
2. Kill arbiter brick, write to the file, bring back arbiter and let self-heal
complete.
3. Next write to the file from mount will hang because the inodelk gets blocked
because of the previous stale locks left behind from self-heal


Additional info:
Downstream bug which found the issue: BZ 1636902

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