[Bugs] [Bug 1218565] New: `gluster volume heal <vol-name> split-brain' shows wrong usage
bugzilla at redhat.com
bugzilla at redhat.com
Tue May 5 09:23:55 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1218565
Bug ID: 1218565
Summary: `gluster volume heal <vol-name> split-brain' shows
wrong usage
Product: GlusterFS
Version: 3.7.0
Component: replicate
Severity: medium
Assignee: bugs at gluster.org
Reporter: ssampat at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Description of problem:
------------------------
Running the following command shows wrong usage message -
# gluster v heal <vol-name> split-brain
Usage: /usr/sbin/glfsheal <VOLNAME> [bigger-file <FILE> | source-brick
<HOSTNAME:BRICKNAME> [<FILE>] | split-brain-info]
Volume heal failed.
The usage above gives the name of the binary instead of the name and format of
the command being run. Another thing to remove from the message is the
`split-brain-info' option as that does not run with the command. See below -
# gluster v heal <vol-name> split-brain split-brain-info
Usage: volume heal <VOLNAME> [enable | disable | full |statistics [heal-count
[replica <HOSTNAME:BRICKNAME>]] |info [healed | heal-failed | split-brain]
|split-brain {bigger-file <FILE> |source-brick <HOSTNAME:BRICKNAME> [<FILE>]}]
Version-Release number of selected component (if applicable):
---------------------------------------------------------------
glusterfs-3.7.0alpha0-0.17.gited96153.el6.x86_64
How reproducible:
------------------
Always
Steps to Reproduce:
--------------------
1. Run the following command and observe the usage message displayed -
# gluster v heal <vol-name> split-brain
Usage: /usr/sbin/glfsheal <VOLNAME> [bigger-file <FILE> | source-brick
<HOSTNAME:BRICKNAME> [<FILE>] | split-brain-info]
Volume heal failed.
Actual results:
-----------------
Usage displayed is incorrect because of the reasons explained above.
Expected results:
------------------
Usage should be correctly displayed.
Additional info:
--
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