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. How reproducible: Always Steps to Reproduce: 1. Select a brick that was previously used to add to a new volume 2. Attempt to add that brick Actual results: Add fails with error messages similar to below /bricks/app or a prefix of it is already part of a volume Expected results: 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 (vbellur)
COMMIT: http://review.gluster.org/5746 committed in master by Anand Avati (avati) ------ commit b2a9cbe5ce61ce170a55fb3dfd7f2d6de9c52f97 Author: Vijay Bellur <vbellur> 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. Change-Id: I79dfeed16a23829a7217cef33ab83f9f0ffae336 Signed-off-by: Vijay Bellur <vbellur> BUG: 1007509 Reviewed-on: http://review.gluster.org/5746 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user