Bug 816051 - CLI: Show proper usage for remove-brick command
Summary: CLI: Show proper usage for remove-brick command
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: shylesh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-04-25 07:19 UTC by shylesh
Modified: 2013-07-24 17:38 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:38:02 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description shylesh 2012-04-25 07:19:44 UTC
Description of problem:

As of now Abort and pause are removed and stop is introduced, these changes should be specified as part of remove-brick command usage.

Comment 1 Anand Avati 2012-04-25 11:06:00 UTC
CHANGE: http://review.gluster.com/3224 (cli: Show proper remove-brick usage) merged in master by Vijay Bellur (vijay@gluster.com)

Comment 2 shylesh 2012-05-07 06:59:44 UTC
 gluster volume remove-brick help 
Usage: volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ... {start|stop|status|commit|force}

shows proper options


Note You need to log in before you can comment on or make changes to this bug.