Red Hat Bugzilla – Bug 1007509
Add Brick Does Not Clear xttr's
Last modified: 2014-04-17 07:47:51 EDT
When trying to add bricks to a volume, if the bricks had been previously used, the add can fail due to fattr's and residual /bricks/app/.glusterfs files.
Steps to Reproduce:
1. Select a brick that was previously used to add to a new volume
2. Attempt to add that brick
Add fails with error messages similar to below
/bricks/app or a prefix of it is already part of a volume
Add works correctly with the fattr's and files removed/set properly.
REVIEW: http://review.gluster.org/5746 (mgmt/glusterd: Relax extended attribute checks for volume create and add brick force.) posted (#4) for review on master by Vijay Bellur (email@example.com)
COMMIT: http://review.gluster.org/5746 committed in master by Anand Avati (firstname.lastname@example.org)
Author: Vijay Bellur <email@example.com>
Date: Sat Aug 31 22:34:02 2013 +0530
mgmt/glusterd: Relax extended attribute checks for volume create and add brick force.
Expectation with force is that user is aware of the consequences of
sanity checks not being triggered.
Signed-off-by: Vijay Bellur <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Anand Avati <firstname.lastname@example.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report.
glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.