REVIEW: http://review.gluster.org/6102 (geo-rep: Increasing the buffer_size for master-salve size comparision.) posted (#1) for review on master by ajeet jha (ajha)
REVIEW: http://review.gluster.org/6102 (geo-rep: Increasing the buffer_size for master-salve size comparision.) posted (#2) for review on master by ajeet jha (ajha)
COMMIT: http://review.gluster.org/6102 committed in master by Anand Avati (avati) ------ commit ef4bb42382a5c9c3ca0907136669a659c2a20311 Author: Ajeet Jha <ajha> Date: Thu Oct 17 13:14:02 2013 +0530 geo-rep: Increasing the buffer_size for master-salve size comparision. The buffer size is increased to 100MB, considering the space required by slave filesystem bookkeeping. Change-Id: Ib296f0e03b4d7a2de6d5ff0ae9ab09a5261e3e7c BUG: 1020154 Signed-off-by: Ajeet Jha <ajha> Reviewed-on: http://review.gluster.org/6102 Reviewed-by: Avra Sengupta <asengupt> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/6844 (geo-replication: gverify should use available_size not 1K-blocks for master_stats) posted (#1) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/6844 (geo-replication: gverify should use disk_size and available_size) posted (#2) for review on master by Harshavardhana (harsha)
COMMIT: http://review.gluster.org/6844 committed in master by Vijay Bellur (vbellur) ------ commit 055c02436fd6ef6984468b33158104770b41e422 Author: Harshavardhana <harsha> Date: Tue Jan 28 17:42:21 2014 -0800 geo-replication: gverify should use disk_size and available_size "commit ef4bb42382a5c9c3ca0907136669a659c2a20311" was incomplete since reduction in sizes doesn't really have any affect on the problem when disks sizes are similar. Actual fix is to verify disk_size and then verify available_size Change-Id: Idb57f606df229c0bdaeda8852c74e84d29109ffc BUG: 1020154 Signed-off-by: Harshavardhana <harsha> Reviewed-on: http://review.gluster.org/6844 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar>
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.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user