Description of problem: ============================== while re-configuring the scrubber frequency, scheduling is not happening based on current time Version-Release number of selected component (if applicable): ===================== mainline How reproducible: Steps to Reproduce: ==================== 1.Create a volume and enable bitrot 2.After some time change the scrubber frequency to hourly but scheduling is happening based on bitrot enable time of the volume not from current time 3. Actual results: Expected results: ===================== while re-configuring the scrubber frequency, scheduling should happen based current time
REVIEW: http://review.gluster.org/11853 (features/bitrot: Fix rescheduling scrub-frequency) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/11853 (features/bitrot: Fix rescheduling scrub-frequency) posted (#2) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/11853 committed in master by Venky Shankar (vshankar) ------ commit 1d0968d5acd10188d4684bfb1d345c72ccefa75a Author: Kotresh HR <khiremat> Date: Thu Aug 6 16:53:22 2015 +0530 features/bitrot: Fix rescheduling scrub-frequency While rescheduling scrub frequency, boot time of the brick was considered where it is not required and also delta is calculated using unsigned int resulting in the loss of fractional part leading to wrong scrub frequency. Boot time is completely removed and delta calculation is simplified. Change-Id: If54697389f663afc86408dc8a01a3ea07e00f2dc BUG: 1251042 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/11853 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user