Bug 765007 (GLUSTER-3275)

Summary:	glusterd should remove 'volume-id' after a remove-brick and delete volume.
Product:	[Community] GlusterFS	Reporter:	krishnan parthasarathi <kparthas>
Component:	cli	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, nsathyan, 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:	DP	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description krishnan parthasarathi 2011-07-29 07:28:24 UTC

With the 'volume-id' extended attribute 'lingering' on bricks that were part of a gluster volume, adding them to a new volume becomes a hindrance. User needs to remove the 'volume-id' extended attribute before (s)he could (re)use the brick in another volume. 'volume-id' is intended to be an internal mechanism by which we prevent a brick from being used in two volumes at the same time. The user must not be made 'aware' of it.

Comment 1 Amar Tumballi 2011-07-29 08:42:10 UTC

We have bought in 'volume-id' extended attribute to prevent re-using of the export bricks from one volume to other. We just need to document the way how it can be reused if that is the intention.

bash# setfattr -x trusted.glusterfs.volume-id <BRICK-PATH> 

With the above command, one can make the brick-path re-exportable again.