REVIEW: http://review.gluster.org/8923 (cluster/afr: Handle EAGAIN properly in inodelk) posted (#1) for review on release-3.4 by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/8923 committed in release-3.4 by Kaleb KEITHLEY (kkeithle) ------ commit dc8a3490e437d25ac2ee94a74778cd16c778514d Author: Pranith Kumar K <pkarampu> 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> Reviewed-on: http://review.gluster.org/8923 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Kaleb KEITHLEY <kkeithle>