REVIEW: http://review.gluster.org/8670 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#1) for review on release-3.4 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/8670 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#2) for review on release-3.4 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/8670 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#3) for review on release-3.4 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/8670 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#4) for review on release-3.4 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/8670 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#5) for review on release-3.4 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/8670 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#6) for review on release-3.4 by Raghavendra G (rgowdapp)
COMMIT: http://review.gluster.org/8670 committed in release-3.4 by Kaleb KEITHLEY (kkeithle) ------ commit 67ccd153a889d81d4cd89534dbce792c111ad1c6 Author: Venkatesh Somyajulu <vsomyaju> Date: Thu Jun 12 14:18:05 2014 +0530 dht/rebalance: Do not allow rebalance when gfid mismatch found Due to race condition, it may so happen that, gfid obtained in readdirp and gfid found by lookup are different for a given name. in that case do no allow the rebalance. Readdirp of an entry will bring the gfid, which will be stored in the inode through inode_link, and when lookup is done and gfid brought by lookup is different from the one stored in the inode, client3_3_lookup_cbk will return ESATLE and error will be captured by rebalance process. Change-Id: Iad839177ef9b80c1dd0e87f3406bcf4cb018e6fa BUG: 1139984 Signed-off-by: Venkatesh Somyajulu <vsomyaju> Reviewed-on: http://review.gluster.org/7973 Reviewed-by: Shyamsundar Ranganathan <srangana> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krutika Dhananjay <kdhananj> Reviewed-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/8670 Reviewed-by: Kaleb KEITHLEY <kkeithle>