REVIEW: http://review.gluster.org/7973 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#1) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/7992 (dht/rebalance: Count as failure if readdir provides an entry on which lookup fails) posted (#1) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/7992 (dht/rebalance: Count it as failure if lookup on readdirp entry fail) posted (#2) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/7973 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#2) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/7973 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#3) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/7973 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#4) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/7973 (dht/rebalance: Do not allow rebalance when gfid mismatch found) posted (#5) for review on master by Raghavendra G (rgowdapp)
COMMIT: http://review.gluster.org/7973 committed in master by Vijay Bellur (vbellur) ------ commit 72c7afcd091605e06a02e7c5de0eff18f0690a82 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: 1104653 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>
REVIEW: http://review.gluster.org/8073 (cluster/dht: make loc->inode instead of loc->parent) posted (#1) for review on master by venkatesh somyajulu (vsomyaju)
COMMIT: http://review.gluster.org/8073 committed in master by Vijay Bellur (vbellur) ------ commit de22a20a76f5cf0af3ca2898f0bfd8324a191e0c Author: Venkatesh Somyajulu <vsomyaju> Date: Mon Jun 16 15:39:57 2014 +0530 cluster/dht: make loc->inode instead of loc->parent parent's inode should be taken from loc->inode. Change-Id: I979b7333efa93b1e8f4c73ccf048d48e308f9289 BUG: 1104653 Signed-off-by: Venkatesh Somyajulu <vsomyaju> Reviewed-on: http://review.gluster.org/8073 Reviewed-by: Krutika Dhananjay <kdhananj> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra G <rgowdapp> Reviewed-by: Vijay Bellur <vbellur>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users