Bug 766532 - Stripe related xattrs are not migrated after replace-brick commit operation
Summary: Stripe related xattrs are not migrated after replace-brick commit operation
Keywords:
Status: CLOSED DUPLICATE of bug 783916
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-12 09:49 UTC by shylesh
Modified: 2015-11-03 23:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-24 09:04:21 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description shylesh 2011-12-12 09:49:03 UTC 
Description of problem:
The xattrs for the stripe volume are not migrated after replace-brick operation

Version-Release number of selected component (if applicable):
3.3.0qa15

How reproducible:
Always

Steps to Reproduce:
1.Create a stripe volume with 2 bricks
2.mount the volume and create some files on it
3.verify the stripe related xattrs for the file in the backend
4. Replace the bricks and commit
5. Now verify the backend bricks for stripe xattrs
   
Actual results:
None of the stripe xattrs are migrated, because of this any further operation on existing files gives I/O error

Expected results:
Xattrs should migrate after replace-brick

Additional info:
Comment 1 krishnan parthasarathi 2012-01-24 09:04:21 UTC 

*** This bug has been marked as a duplicate of bug 783916 ***
Note You need to log in before you can comment on or make changes to this bug.