I nuked the entire partition with mkfs, just to be *sure*, and I still get the error message:
volume create: gv0: failed: /brick1/gv0 is already part of a volume
Clearly, there's some bit of data being kept somewhere else besides in /brick1?
On 2015-02-11 01:03, Kaushal M wrote:
This happens because of 2 things,
1. GlusterFS writes an extended attribute containing the volume-id to every brick directory when a volume is created. This is done to prevent data being written to the root partition, in case the partition containing the brick wasn't mounted for any reason.
2. Deleting a GlusterFS volume does not remove any data in the brick directories and the brick directories themselves. We leave the decision of cleaning up the data to the user. The extended attribute is also not removed, so that an unused brick is not inadvertently added to another volume as it could lead to losing existing data.
So if you want to reuse a brick, you need to clean it up and recreate the brick directory.
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users