Bug 816884 - [glusterfs-3.3.0qa39]: if one of the bricks of a volume is down, statedump cannot be taken
Summary: [glusterfs-3.3.0qa39]: if one of the bricks of a volume is down, statedump ca...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raghavendra Bhat
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-04-27 08:59 UTC by Raghavendra Bhat
Modified: 2013-07-24 17:40 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:40:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: glusterfs-3.3.0qa42
Embargoed:

Attachments (Terms of Use)

Description Raghavendra Bhat 2012-04-27 08:59:38 UTC 
Description of problem:
Suppose one of the bricks of the volume is down, then statedump of that volume cannot be taken via the cli command.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a volume, start it.
2. Kill one of the bricks
3. Issue gluster volume statedump <volname> command
  
Actual results:

statedumps of the bricks that are running are also not taken.

Expected results:

cli command for statedump should be able to get the statedumps of the bricks that are running.
Additional info:
Comment 1 Anand Avati 2012-05-01 17:25:47 UTC 
CHANGE: http://review.gluster.com/3237 (mgmt/glusterd: take the statedumps of running bricks if one of the bricks is down) merged in master by Vijay Bellur (vijay)
Comment 2 Raghavendra Bhat 2012-05-21 09:24:58 UTC 
Checked with glusterfs-3.3.0qa42. Now statedump of the existing bricks can be taken.
Note You need to log in before you can comment on or make changes to this bug.