Bug 957917

Summary:	gluster create volume doesn't cleanup after its self if the create fails.
Product:	[Community] GlusterFS	Reporter:	Mark <mark.a.sloan>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	pre-release	CC:	amukherj, bugs, gluster-bugs, redhat.bugs, rwheeler
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1056551 (view as bug list)		Environment:
Last Closed:	2015-08-08 13:49:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1056551

Description Mark 2013-04-29 22:27:39 UTC

Description of problem:

During a volume create bricks are marked as being part of a volume. If the create fails for some reason,  this is not cleaned up and the bricks are still marked as being used. the volume may not be deleted by a volume delete command and the volume create command can't use those bricks until they are cleaned up. 



Version-Release number of selected component (if applicable):
glusterfs-server-3.4.0-0.3.alpha3.el6.x86_64
glusterfs-fuse-3.4.0-0.3.alpha3.el6.x86_64
glusterfs-3.4.0-0.3.alpha3.el6.x86_



How reproducible:
every time

Steps to Reproduce:
1. create a situation where a volume create will fail on one of the nodes, but succeed on the others. 
2. run a create volume command on all nodes (including the one that will fail, e.g. for iptable rule)
3. try a volume delete or a volume create using the same bricks. 

  
Actual results:


Expected results:
a failed volume create should clean up after it's self, without the user having to use the steps at http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/ to clean up. 

Additional info:

Comment 1 Richard 2013-09-24 07:44:35 UTC

I'd be interested in seeing this feature added to Gluster.

Comment 2 Atin Mukherjee 2015-08-08 13:49:17 UTC

I don't think we will be working on this bug in near future. We do have a workaround of using 'force' option as part of volume create. Considering that I don't think its a high priority bug and can be closed. Feel free to reopen with proper justification.