[Bugs] [Bug 1142020] data loss when rebalance + renames are in progress and bricks from replica pairs goes down and comes back
bugzilla at redhat.com
bugzilla at redhat.com
Tue Sep 16 06:02:31 UTC 2014
https://bugzilla.redhat.com/show_bug.cgi?id=1142020
--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/8744 committed in release-3.6 by Vijay Bellur
(vbellur at redhat.com)
------
commit 3719996a2d31d492d8a3b3f7defe57c2108c3f45
Author: Pranith Kumar K <pkarampu at redhat.com>
Date: Sun Sep 14 16:51:25 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.
BUG: 1142020
Change-Id: Iee3f5990be75e10f8accec9bc3856e3f76d1593c
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
Reviewed-on: http://review.gluster.org/8744
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur 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=XL5OxvHDvc&a=cc_unsubscribe
More information about the Bugs
mailing list