Description of problem: if provided wrong option for gluster command for disperse volume, Usage displays about replica. Could mislead customers. [root@aspandey ~]# gluster volume remove-brick gfs aspandey:/brick/dist/A11 aspandey:/brick/dist/A12 aspandey:/brick/dist/A13 aspandey:/brick/dist/A14 aspandey:/brick/dist/A15 aspandey:/brick/dist/A16 sta Usage: volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ... <start|stop|status|commit|force> [root@aspandey ~]# [root@aspandey ~]# gluster v heal 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>]}] [root@aspandey ~]# gluster v add-brick gfs Usage: volume add-brick <VOLNAME> [<stripe|replica> <COUNT>] <NEW-BRICK> ... [force] Version-Release number of selected component (if applicable): Usage: volume add-brick <VOLNAME> [<stripe|replica> <COUNT>] <NEW-BRICK> ... [force] [root@aspandey ~]# gluster --version glusterfs 3.8dev built on Jun 30 2015 18:11:45 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. [root@aspandey ~]# How reproducible: 100% Steps to Reproduce: 1.Create disperse volume 2.Provide wrong options for the above commands for disperse volumes Actual results: wrong usage information Expected results: Usage: must contain the information about all or targeted "volume type" Additional info:
REVIEW: http://review.gluster.org/15540 (cli : Displaying the proper error message for remove-brick) posted (#1) for review on master by Muthu Vigneshwaran
REVIEW: http://review.gluster.org/15540 (cli : Displaying the proper error message for remove-brick) posted (#2) for review on master by Muthu Vigneshwaran
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.