Bug 765587 (GLUSTER-3855) - Replicate: no xattr, all zero xattr self-heal bug
Summary: Replicate: no xattr, all zero xattr self-heal bug
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3855
Product: GlusterFS
Classification: Community
Component: replicate
Version: pre-release
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact: Sachidananda Urs
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2011-12-08 05:53 UTC by Sachidananda Urs
Modified: 2013-07-24 17:16 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:16:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Sachidananda Urs 2011-12-08 05:53:47 UTC 
When one of the file has replicate xattrs set to all zero (All is well) and when the corresponding file does not have any xattrs set (FOOL?). What is the expected behavior?

Currently it does not self-heal.
Comment 1 Rodrigo Severo 2012-04-10 13:27:25 UTC 
If you stat this file, what you get? The files current data or a input/output error?

Anyway I believe self heal should occur from the "All is well" to the "FOOL" bricks.
Comment 2 Anand Avati 2012-05-19 03:11:13 UTC 
CHANGE: http://review.gluster.com/3088 (cluster/afr: Determining sources should do both fxattrop, fstat) merged in master by Anand Avati (avati)
Comment 3 Anand Avati 2012-05-19 03:12:31 UTC 
CHANGE: http://review.gluster.com/3089 (cluster/afr: Mark zero size file as sink in absense of xattrs.) merged in master by Anand Avati (avati)
Comment 4 Anand Avati 2012-05-19 03:14:04 UTC 
CHANGE: http://review.gluster.com/3090 (cluster/afr: Handle files w.o. xattrs and size mismatch.) merged in master by Anand Avati (avati)
Comment 5 Anand Avati 2012-05-19 03:16:48 UTC 
CHANGE: http://review.gluster.com/3091 (cluster/afr: Perform conservative merge on dir with xattr split-brain) merged in master by Anand Avati (avati)
Comment 6 Rodrigo Severo 2012-05-19 10:33:07 UTC 
In what release are these changes expected to first appear?
Comment 7 Pranith Kumar K 2012-06-13 07:09:21 UTC 
Rodrigo,
      The fixes are present in 3.2.7

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