[Bugs] [Bug 1216303] Fixes for data self-heal in ec

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1216303



--- Comment #18 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10692 committed in release-3.7 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit f54b232b3cc61ee9ca76288958537b53de64de53
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Sat Apr 25 15:58:09 2015 +0530

    cluster/ec: data heal implementation for ec

    Data self-heal:
    1) Take inode lock in domain 'this->name:self-heal' on 0-0 range (full
file),
       So that no other processes try to do self-heal at the same time.
    2) Take inode lock in domain 'this->name' on 0-0 range (full file),
    3) perform fxattrop+fstat and get the xattrs on all the bricks
    3) Choose the brick with ec->fragment number of same version as source
    4) Truncate sinks
    5) Unlock lock taken in 2)
    5) For each block take full file lock, Read from sources write to the
sinks, Unlock
    6) Take full file lock and see if the file is still sane copy i.e. File
didn't become unusable while the bricks are offline.
       Update mtime to before healing
    7) xattrop with -ve values of 'dirty' and difference of highest and its own
       version values for version xattr
    8) unlock lock acquired in 6)
    9) unlock lock acquired in 1)

    Change-Id: I6f4d42cd5423c767262c9d7bb5ca7767adb3e5fd
    BUG: 1216303
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/10384
    Reviewed-on: http://review.gluster.org/10692
    Tested-by: Gluster Build System <jenkins at build.gluster.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.