Bug 1007509

Summary: Add Brick Does Not Clear xttr's
Product: [Community] GlusterFS Reporter: Vijay Bellur <vbellur>
Component: glusterdAssignee: Vijay Bellur <vbellur>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 3.4.0CC: chhudson, dpati, gluster-bugs, rhs-bugs, rnelson, rwheeler, sabose, vbellur, wduffee
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.5.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 960069
: 1045991 (view as bug list) Environment:
Last Closed: 2014-04-17 11:47:51 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:
Bug Depends On:    
Bug Blocks: 960069, 1045991    

Description Vijay Bellur 2013-09-12 15:48:28 UTC
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.

Comment 1 Anand Avati 2013-09-25 17:43:15 UTC
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)

Comment 2 Anand Avati 2013-10-18 00:16:28 UTC
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>

Comment 3 Niels de Vos 2014-04-17 11:47:51 UTC
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