+++ This bug was initially created as a clone of Bug #1007509 +++ 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. --- Additional comment from Anand Avati on 2013-09-25 13:43:15 EDT --- 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) --- Additional comment from Anand Avati on 2013-10-17 20:16:28 EDT --- 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>
Verified and works fine with glusterfs-3.4.0.53rhs-1.el6rhs.x86_64. Tested the following scenarions 1) Created a new volume with bricks which are part of another volume which was deleted. 2) Added a brick to the existing volume which was part of another volume which was deleted. 3) Removed a brick from the existing volume and added it to the new volume.
Can you please verify the doc text for technical accuracy?
Doc Text looks good to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0208.html