Bug 816884

Summary:	[glusterfs-3.3.0qa39]: if one of the bricks of a volume is down, statedump cannot be taken
Product:	[Community] GlusterFS	Reporter:	Raghavendra Bhat <rabhat>
Component:	glusterd	Assignee:	Raghavendra Bhat <rabhat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	gluster-bugs, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:40:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:	glusterfs-3.3.0qa42	Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	817967

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.