Bug 829675

Summary: GlusterFS: Can't remove and re-add the same brick
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Daniel Paikov <dpaikov>
Component: glusterdAssignee: krishnan parthasarathi <kparthas>
Status: CLOSED DUPLICATE QA Contact: Sudhir D <sdharane>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: amarts, gluster-bugs, hateya, ndevos, nsathyan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-11 07:17:10 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:
Attachments:
Description Flags
vdsm.log
none
glusterfs log none

Description Daniel Paikov 2012-06-07 09:21:20 UTC
Created attachment 590141 [details]
vdsm.log

* Create a brick on host:/dir
* Remove the brick
* Try to create the same brick
* 2nd create fails because the brick already exists, even though the brick was removed and doesn't appear in "gluster volume info".

Comment 1 Daniel Paikov 2012-06-07 09:23:09 UTC
Created attachment 590142 [details]
glusterfs log

Comment 3 Niels de Vos 2012-06-07 12:49:08 UTC
There are some procedures explained in https://access.redhat.com/knowledge/solutions/135343 that can help.

The (depending on view point) bug here, is that there are still some extended attributes set on the directory of the brick. After removing these, you should be able to re-use the existing brick.

Comment 4 Niels de Vos 2012-06-07 14:17:01 UTC
Bug 765572 mentions that a script can be used to remove the xattrs.

A description of it's usage can be found here:
- http://review.gluster.com/781

Comment 5 Niels de Vos 2012-06-11 07:17:10 UTC
Bug 812214#c10 contains a description about this problem as well. Closing this as a duplicate.

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