[Bugs] [Bug 1306922] New: Self heal command gives error "Launching heal operation to perform index self heal on volume vol0 has been unsuccessful"

bugzilla at redhat.com bugzilla at redhat.com
Fri Feb 12 08:26:32 UTC 2016


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

            Bug ID: 1306922
           Summary: Self heal command gives error "Launching heal
                    operation to perform index self heal on volume vol0
                    has been unsuccessful"
           Product: GlusterFS
           Version: 3.7.7
         Component: replicate
          Keywords: Triaged
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org
        Depends On: 1294612, 1302291, 1200252



Description of problem:
1. create a 1x3 replica using a 3 node cluster
2. Kill one brick, run 'gluster vol heal <volname>`

RCA:
If any of the bricks is down, glustershd of that node sends a -1 op_ret to
glusterd which eventually propagates it to the CLI. If op_ret is non zero, CLI
prints "Launching heal...unsuccessful". For the bricks that are up and need
heal, the healing happens without any issues.

A reasonable fix seems to be to print a more meaningful message on the CLI like
"Launching heal operation to perform index self heal on volume vol0 has not
been been successful on all nodes. Please check if all brick processes are
running."


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1200252
[Bug 1200252] Self heal command gives error "Launching heal operation to
perform index self heal on volume vol0 has been unsuccessful"
https://bugzilla.redhat.com/show_bug.cgi?id=1294612
[Bug 1294612] Self heal command gives error "Launching heal operation to
perform index self heal on volume vol0 has been unsuccessful"
https://bugzilla.redhat.com/show_bug.cgi?id=1302291
[Bug 1302291] Self heal command gives error "Launching heal operation to
perform index self heal on volume vol0 has been unsuccessful"
-- 
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