Bug 767545 - [7235e5b1af090ffc9d87ac59daadf7926433b495] gluster volume statedump volname not working
Summary: [7235e5b1af090ffc9d87ac59daadf7926433b495] gluster volume statedump volname n...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Vinayaga Raman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2011-12-14 10:43 UTC by Rahul C S
Modified: 2014-03-31 01:28 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description Rahul C S 2011-12-14 10:43:44 UTC
Description of problem:
gluster volume statedump <volname> does not do statedump of the bricks.
when u give argument to this it works. 

For ex: gluster volume statedump <volname> all 
does statedump of all the bricks.

By default if no argument is given, it should perform the statedump of all the bricks.

Comment 1 Anand Avati 2011-12-19 16:49:40 UTC
CHANGE: http://review.gluster.com/799 (Default option to be set to "all" if no option is given to volume statedump cli command.) merged in master by Vijay Bellur (vijay)

Comment 2 Rahul C S 2012-04-05 06:38:32 UTC
Default option is all & when the statedump operation is issued, performs the statedump for all bricks.


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