Description of problem: ======================= Scrub tunable - (scrub-throttle, scrub-frequency, pause/resume) are giving message success on CLI but don't have any impact on scrub functionality Version-Release number of selected component (if applicable): ============================================================= 0.803.gitf64666f.el6.x86_64 How reproducible: ================= always Steps to Reproduce: =================== 1. create and mount volume. 2. enable bitrot 3. create few files. 4. change tunables and check impact [root@rhs-client37 ~]# gluster volume bitrot rac1 scrub-frequency daily volume bitrot: success [root@rhs-client37 ~]# gluster volume bitrot rac1 scrub-throttle frozen volume bitrot: success [root@rhs-client37 ~]# gluster volume bitrot rac1 scrub pause volume bitrot: success Actual Result:- =============== able to change tunable and it says success but don't have any impact on scrub process
REVIEW: http://review.gluster.org/10409 (features/bitrot: scrubber should crawl based on the scrubber frequency value) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10409 (features/bitrot: scrubber should crawl based on the scrubber frequency value) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10521 (features/bitrot: Scrubber pause/resume) posted (#1) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/10409 (features/bitrot: scrubber should crawl based on the scrubber frequency value) posted (#3) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10409 (features/bitrot: scrubber should crawl based on the scrubber frequency value) posted (#4) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10602 (features/bitrot: scrubber should crawl based on the scrubber frequency value) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10521 (features/bitrot: Scrubber pause/resume) posted (#3) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/10521 (features/bitrot: Scrubber pause/resume) posted (#4) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/10521 (features/bitrot: Scrubber pause/resume) posted (#5) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10602 (features/bitrot: scrubber should crawl based on the scrubber frequency value) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10602 (features/bitrot: scrubber should crawl based on the scrubber frequency value) posted (#5) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10602 (features/bitrot: scrubber should crawl based on the scrubber frequency value) posted (#6) for review on master by Gaurav Kumar Garg (ggarg)
COMMIT: http://review.gluster.org/10602 committed in master by Vijay Bellur (vbellur) ------ commit 7c1415fa591172765ab1e7dc1b049bf162d53788 Author: Gaurav Kumar Garg <ggarg> Date: Wed May 6 14:23:34 2015 +0530 features/bitrot: scrubber should crawl based on the scrubber frequency value Currently scrubber is crawling all the files continuously. It should crawl files based on the scrubber frequency which user have set. By default scrubber crawling frequency value will be biweekly. Change-Id: I5762a92c1e700134cfe4283d1f631904adbfe31d BUG: 1208131 Signed-off-by: Gaurav Kumar Garg <ggarg> Reviewed-on: http://review.gluster.org/10602 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra Bhat <raghavendra> Reviewed-by: Vijay Bellur <vbellur>
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.
Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.
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