[Bugs] [Bug 1402841] New: Files remain unhealed forever if shd is disabled and re-enabled while healing is in progress.

[bugzilla at redhat.com]

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

            Bug ID: 1402841
           Summary: Files remain unhealed forever if shd is disabled and
                    re-enabled while healing is in progress.
           Product: GlusterFS
           Version: mainline
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org



Description of problem:

1. Create a 1x2 replica vol using a 2 node cluster.
2. Fuse mount the vol and create 2000 files
3. Bring one brick down, write to those files, leading to 2000 pending data
heals.
4. Bring back the brick and launch index heal
5. The shd log on the source brick prints completed heals for the the processed
files.
6. Before the heal completes, do a `gluster vol set volname self-heal-daemon
off`
7. The heal stops as expected.
8. Re-enable the shd: `gluster vol set volname self-heal-daemon on`
9. Observe the shd log, we don't see any files getting healed.
10. Launching index heal manually also has no effect.

The only workaround is to restart shd with a `volume start force`.

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