Bug 807428 - Gluster volume status command produces truncated result when a node is down
Summary: Gluster volume status command produces truncated result when a node is down
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.3-beta
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kaushal
QA Contact: Anush Shetty
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-27 18:40 UTC by Gareth Bult
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

Description Gareth Bult 2012-03-27 18:40:11 UTC
gluster volume stats

- works OK if all nodes are up, but breaks it one or more nodes are not available. Typically the list of bricks stops as soon as it comes to a brick on a downed node.

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

To reproduce:

visit random node
"service glusterd stop"
visit random client
"gluster volume status"
- result should be truncated when it reached downed node.

Have tried on 2 stripe replica and 4 stripe replica.  

Conditions;

The faulty node must contain an active volume.
The output of "gluster volume status" will be different depending on which node you take out.

Comment 1 Kaushal 2012-03-30 05:00:29 UTC
Fixed in change http://review.gluster.com/3016 for bug https://bugzilla.redhat.com/show_bug.cgi?id=803676

Comment 2 Anush Shetty 2012-05-31 09:27:09 UTC
Verified with 3.3.0qa45


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