Red Hat Bugzilla – Bug 765007
glusterd should remove 'volume-id' after a remove-brick and delete volume.
Last modified: 2015-11-03 18:03:41 EST
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.
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.