[Bugs] [Bug 1183716] Force replace-brick lead to the persistent write(use dd) return Input/output error

[bugzilla at redhat.com]

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



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9560 committed in release-3.6 by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit 1c14d8268b36e401ad7ac74ba3f082100fbe2bcc
Author: Xavier Hernandez <xhernandez at datalab.es>
Date:   Wed Jan 7 12:29:48 2015 +0100

    ec: Fix failures with missing files

    When a file does not exist on a brick but it does on others, there
    could be problems trying to access it because there was some loc_t
    structures with null 'pargfid' but 'name' was set. This forced
    inode resolution based on <pargfid>/name instead of <gfid> which
    would be the correct one. To solve this problem, 'name' is always
    set to NULL when 'pargfid' is not present.

    Another problem was caused by an incorrect management of errors
    while doing incremental locking. The only allowed error during an
    incremental locking was ENOTCONN, but missing files on a brick can
    be returned as ESTALE. This caused an EIO on the operation.

    This patch doesn't care of errors during an incremental locking. At
    the end of the operation it will check if there are enough successfully
    locked bricks to continue or not.

    This is a backport of http://review.gluster.org/9407/

    Change-Id: I9360ebf8d819d219cea2d173c09bd37679a6f15a
    BUG: 1183716
    Signed-off-by: Xavier Hernandez <xhernandez at datalab.es>
    Reviewed-on: http://review.gluster.org/9560
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=i9MJslKhKq&a=cc_unsubscribe