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

bugzilla at redhat.com bugzilla at redhat.com
Sun May 10 00:30:53 UTC 2015


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



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10701 committed in release-3.7 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit 72f80aeba1268ed4836c10aee5fa41b6a04194e9
Author: Xavier Hernandez <xhernandez at datalab.es>
Date:   Wed Jan 7 12:29:48 2015 +0100

    ec: Fix failures with missing files

          Backport of http://review.gluster.com/9407

    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.

    BUG: 1220011
    Change-Id: I4a1e6235d80e20ef7ef12daba0807b859ee5c435
    Signed-off-by: Xavier Hernandez <xhernandez at datalab.es>
    Reviewed-on: http://review.gluster.org/10701
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    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.


More information about the Bugs mailing list