REVIEW: http://review.gluster.org/5577 (cluster/dht: Del GF_READDIR_SKIP_DIRS key from dict for first_up) posted (#2) for review on master by Shishir Gowda (sgowda)
COMMIT: http://review.gluster.org/5577 committed in master by Vijay Bellur (vbellur) ------ commit 2a195787746a6bfd3e1da6bf38c657ae0ccda24d Author: shishir gowda <sgowda> Date: Mon Aug 12 17:25:12 2013 +0530 cluster/dht: Del GF_READDIR_SKIP_DIRS key from dict for first_up Currently, we sent GF_READDIR_SKIP_DIRS for all subvolumes if first_subvol != first_up_subvolume. Also first_up_subvolume can change with-in the life of a call and cbk. Saving the first_up_subvol in dht_local for checks. Change-Id: I6e369e63f29c9761993f2a66ed768c424bb44d27 BUG: 996474 Signed-off-by: shishir gowda <sgowda> Reviewed-on: http://review.gluster.org/5577 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Reviewed-by: Vijay Bellur <vbellur> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/6468 (cluster/dht: Del GF_READDIR_SKIP_DIRS key from dict for first_up) posted (#1) for review on release-3.4 by Shishir Gowda (gowda.shishir)
COMMIT: http://review.gluster.org/6468 committed in release-3.4 by Vijay Bellur (vbellur) ------ commit 6677b97f2d17699c74779922cf310adf8bff5558 Author: shishir gowda <gowda.shishir> Date: Tue Dec 10 14:42:05 2013 +0530 cluster/dht: Del GF_READDIR_SKIP_DIRS key from dict for first_up Currently, we sent GF_READDIR_SKIP_DIRS for all subvolumes if first_subvol != first_up_subvolume. Also first_up_subvolume can change with-in the life of a call and cbk. Saving the first_up_subvol in dht_local for checks. Back porting fix http://review.gluster.org/5577 BUG: 996474 Change-Id: I67b5bbe781e12812557b569b7d0a0beba4224159 Signed-off-by: shishir gowda <gowda.shishir> Reviewed-on: http://review.gluster.org/6468 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