Bug 763749 (GLUSTER-2017)

Summary:	Stopping an already stopped volume reports "unsuccessful"
Product:	[Community] GlusterFS	Reporter:	Vikas Gorur <vikas>
Component:	cli	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.1.0	CC:	gluster-bugs, rabhat, vraman
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:
Embargoed:

Description Vikas Gorur 2010-10-26 22:03:36 UTC

[root@brick5 ~]# gluster volume stop perf
Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y
Stopping volume perf has been successful
[root@brick5 ~]# gluster volume stop perf
Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y
Stopping volume perf has been unsuccessful

The second attempt to stop should simply say, "volume perf already stopped". Since the CLI knows the state of the volume, there is no reason not to check it before trying to stop the volume.

Comment 1 Raghavendra Bhat 2010-10-27 02:42:37 UTC

Vikas, a bug has already been filed for it (2010), and I have sent a patch for it. It says "volume is not in started state" if an attempt is made to stop a volume which is already stopped or just created and has not been started. But 2nd time also it asks for confirmation because the state of a volume is maintained by glusterd and not CLI. Marking this as the duplicate of it.

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