[Bugs] [Bug 1141733] 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=1141733



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/8739 committed in release-3.5 by Niels de Vos
(ndevos at redhat.com) 
------
commit f67921dec0ab5db6c7c0bc1b00459dbcfa1d568d
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Mon Sep 15 14:22:44 2014 +0530

    cluster/afr: Handle EAGAIN properly in inodelk

    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.

    Change-Id: I07673f8873263da334e03f35c6cdb5db9410a616
    BUG: 1141733
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/8739
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    Reviewed-by: Niels de Vos <ndevos 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=YSZIvKPKvE&a=cc_unsubscribe