REVIEW: http://review.gluster.org/4989 (cluster/dht: Do migration inprog/complete check only if ENOENT) posted (#2) for review on master by Shishir Gowda (sgowda)
COMMIT: http://review.gluster.org/4989 committed in master by Vijay Bellur (vbellur) ------ commit bca2449cb59727196d328462c912a1be20117b9d Author: shishir gowda <sgowda> Date: Mon May 13 09:51:49 2013 +0530 cluster/dht: Do migration inprog/complete check only if ENOENT Additionally, update op_errno to the lasted failure. If failures found in complete_check, error returned would be EUCLEAN instead of the right failure (in this case ENOENT) Change-Id: Ib813867f4b817af651627b9ea07b0b09fa2b26ce BUG: 966852 Signed-off-by: shishir gowda <sgowda> Reviewed-on: http://review.gluster.org/4989 Reviewed-by: Amar Tumballi <amarts> Reviewed-by: Vijay Bellur <vbellur> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/6495 (cluster/dht: Do migration inprog/complete check only if ENOENT) posted (#1) for review on release-3.4 by Anand Avati (avati)
REVIEW: http://review.gluster.org/6495 (cluster/dht: Do migration inprog/complete check only if ENOENT) posted (#2) for review on release-3.4 by Anand Avati (avati)
COMMIT: http://review.gluster.org/6495 committed in release-3.4 by Vijay Bellur (vbellur) ------ commit b562ace8f7525f6d06555d4f02ac48fec82f23ad Author: Anand Avati <avati> Date: Wed Dec 11 13:57:13 2013 -0800 cluster/dht: Do migration inprog/complete check only if ENOENT Additionally, update op_errno to the lasted failure. If failures found in complete_check, error returned would be EUCLEAN instead of the right failure (in this case ENOENT) Change-Id: Ib813867f4b817af651627b9ea07b0b09fa2b26ce BUG: 966852 Original-author: shishir gowda <sgowda> Signed-off-by: Anand Avati <avati> Reviewed-on: http://review.gluster.org/6495 Tested-by: Gluster Build System <jenkins.com> 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