Bug 764472 (GLUSTER-2740)

Summary:	volume top brick option with hostname instead of <ip-addr> resulted in cli unresponsiveness
Product:	[Community] GlusterFS	Reporter:	M S Vishwanath Bhat <vbhat>
Component:	unclassified	Assignee:	shishir gowda <sgowda>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, mzywusko, nsathyan, vijay
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description M S Vishwanath Bhat 2011-04-13 08:07:58 UTC

I ran the following command 
#gluster volume top <volname> open brick FC-1:/data/vishwa/brick1 list-cnt 10

The above command exited with non-zero exit status. But after that many cli command didn't work. I keep getting "operation failed" for all profile/top commands. I can't even stop the volume, or profile. All glusterd and server processes were up and running.

I have archived the logs since the log file was too big.

Comment 1 M S Vishwanath Bhat 2011-04-13 08:58:10 UTC

I hit this issue only when testing using multiple vm's. When tested in my local machine where all the bricks of the server present in same machine, this issue will not be hit.

Comment 2 shishir gowda 2011-04-19 06:37:21 UTC

Works for me.
Might be a setup issue.