[Bugs] [Bug 1151308] data loss when rebalance + renames are in progress and bricks from replica pairs goes down and comes back

[bugzilla at redhat.com]

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



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/8923 committed in release-3.4 by Kaleb
KEITHLEY (kkeithle at redhat.com) 
------
commit dc8a3490e437d25ac2ee94a74778cd16c778514d
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Mon Sep 15 14:22:44 2014 +0530

    cluster/afr: Handle EAGAIN properly in inodelk

            Backport of http://review.gluster.org/8739

    Problem:
    When one of the brick is taken down and brough back up in a replica pair,
locks
    on that brick will be allowed. Afr returns inodelk success even when one of
the
    bricks already has the lock taken.

    Fix:
    If any brick returns EAGAIN return failure to parent xlator.

    Note: This change only works for non-blocking inodelks. This patch
addresses
    dht-synchronization which uses non-blocking locks for rename. Blocking lock
is
    issued by only one of the rebalance processes. So for now there is no
    possibility of deadlock.

    BUG: 1151308
    Change-Id: I72f15d8789442c29b5c7be2d5dabf7bae6bfa845
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/8923
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle 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=1EnVwbpMpj&a=cc_unsubscribe