REVIEW: http://review.gluster.org/5056 (cluster/dht: Ignore decommissioned subvol in overlap optimization) posted (#2) for review on master by Shishir Gowda (sgowda)
COMMIT: http://review.gluster.org/5056 committed in master by Anand Avati (avati) ------ commit 4f63b631dce4cb97525ee13fab0b2a789bcf6b15 Author: shishir gowda <sgowda> Date: Tue May 21 16:29:32 2013 +0530 cluster/dht: Ignore decommissioned subvol in overlap optimization Change-Id: Ib727948c6e21b19fd509f258ff0aea1c5d1a84d1 BUG: 966845 Signed-off-by: shishir gowda <sgowda> Reviewed-on: http://review.gluster.org/5056 Reviewed-by: Amar Tumballi <amarts> Reviewed-by: Jeff Darcy <jdarcy> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/6517 (cluster/dht: Ignore decommissioned subvol in overlap optimization) posted (#1) for review on release-3.4 by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/6517 committed in release-3.4 by Vijay Bellur (vbellur) ------ commit 8abd500b79233c292a6098fe4e3672cacb2017d0 Author: shishir gowda <sgowda> Date: Tue May 21 16:29:32 2013 +0530 cluster/dht: Ignore decommissioned subvol in overlap optimization Change-Id: Ib727948c6e21b19fd509f258ff0aea1c5d1a84d1 BUG: 966845 Signed-off-by: shishir gowda <sgowda> Reviewed-on: http://review.gluster.org/5056 Reviewed-by: Amar Tumballi <amarts> Reviewed-by: Jeff Darcy <jdarcy> Tested-by: Gluster Build System <jenkins.com> Reviewed-on: http://review.gluster.org/6517 Reviewed-by: Shishir Gowda <gowda.shishir> Reviewed-by: Vijay Bellur <vbellur>
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.4.3, please reopen this bug report. glusterfs-3.4.3 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should already be or become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. The fix for this bug likely to be included in all future GlusterFS releases i.e. release > 3.4.3. In the same line the recent release i.e. glusterfs-3.5.0 [3] likely to have the fix. You can verify this by reading the comments in this bug report and checking for comments mentioning "committed in release-3.5". [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/5978 [2] http://news.gmane.org/gmane.comp.file-systems.gluster.user [3] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137