Bug 764798 (GLUSTER-3066) - aggregate xattrs in stripe lookup
Summary: aggregate xattrs in stripe lookup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3066
Product: GlusterFS
Classification: Community
Component: stripe
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
: GLUSTER-3132 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-21 08:46 UTC by shishir gowda
Modified: 2013-12-09 01:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: master


Attachments (Terms of Use)

Description shishir gowda 2011-06-21 08:46:12 UTC
Since stripe_setxattr is default done only on the first child, we could loose them if the local->dict was set to non-first child.

Issue was seen when running dist-stripe. layout self heal was getting triggered as it was detecting holes

Comment 1 Anand Avati 2011-06-22 12:40:46 UTC
PATCH: http://patches.gluster.com/patch/7573 in master (Stripe lookup: aggregate xattrs)

Comment 2 shishir gowda 2011-07-06 02:33:28 UTC
*** Bug 3132 has been marked as a duplicate of this bug. ***

Comment 3 liuben 2011-07-06 23:10:19 UTC
After apply the patch, thers is another problem.

files/directory can create/remove, but some files contents are invalid. For example, autogen.sh in gluster 3.2.1 sources, 

^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

Comment 4 shishir gowda 2011-07-07 00:38:27 UTC
Hi Liuben,

This bug dealt with layout mismatch in a distributed-stripe setup, and the patch in question fixes the issue at hand.

Please open a new bug for the issue you are running into.

By moving the status to verified,wontfix, you are breaking the process of verifying the bugs by QA.

With regards,
Shishir

Comment 5 Rahul C S 2011-08-19 03:05:03 UTC
This is just a code change, verified in editor.


Note You need to log in before you can comment on or make changes to this bug.