Bug 763623 (GLUSTER-1891)

Summary:	wrong message during volume stop with removed-detached brick
Product:	[Community] GlusterFS	Reporter:	Lakshmipathi G <lakshmipathi>
Component:	cli	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	3.1-alpha	CC:	gluster-bugs, vijay
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTP	Mount Type:	All
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Lakshmipathi G 2010-10-11 06:33:18 UTC

remove a brick from 3-dht cluster and did a peer detach on removed-brick.

On the removed-brick volume stop says "successful" - though it didn't stop the volume. 

removed-birck# gluster volume stop dht44
Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y
Stopping volume dht44 has been successful

Comment 1 Pranith Kumar K 2010-10-11 10:38:18 UTC

This bug should not be observed once the bug 763517 is fixed. So making this a dup.

*** This bug has been marked as a duplicate of bug 1785 ***