Description of problem: ======================== Currently, the command 'gluster volume bitrot <volname> scrub-frequency' can set the frequency to hourly/daily/weekly/biweekly/monthly. For testing, we set the frequency to the minimum possible, i.e., an hour. After corrupting a file, we are forced to wait out an entire hour (or more) for the scrubber to mark the file as 'corrupted'. The above mentioned step is one of the common task that is followed for most test cases. This leads to unnecessary inconvenience when testing bitrot feature. Needless to say, automation also takes close to 3 days, just because of the mandatory requirement of waiting for an hour before doing any validation. I understand the need to reduce time < hour would never arise in the field, but it would be good to have such an option provided for testing and regression purposes, in the upcoming releases. Version-Release number of selected component (if applicable): ============================================================ 3.7.9-3 Additional info: ================ [root@dhcp35-13 ~]# gluster v bitrot ozone Usage: volume bitrot <VOLNAME> {enable|disable} | volume bitrot <volname> scrub-throttle {lazy|normal|aggressive} | volume bitrot <volname> scrub-frequency {hourly|daily|weekly|biweekly|monthly} | volume bitrot <volname> scrub {pause|resume|status} [root@dhcp35-13 ~]#
Upstream Patches: http://review.gluster.org/#/c/14836/1 (master)
Upstream Patches: http://review.gluster.org/#/c/14836/ (master) http://review.gluster.org/#/c/14887/ (3.7) http://review.gluster.org/#/c/14890/ (3.8)
(In reply to Kotresh HR from comment #5) > Upstream Patches: > http://review.gluster.org/#/c/14836/ (master) > http://review.gluster.org/#/c/14887/ (3.7) > http://review.gluster.org/#/c/14890/ (3.8) Fix is available in rhgs-3.2.0 as part of rebase to GlusterFS 3.8.4
Tested and verified this on the build 3.8.4-2 We are able to set the scrub-frequency of a bitrot enabled volume to a minute. The logs /var/log/glusterfs/bitd.log and /var/log/glusterfs/scrub.log do reflect the minute timing. It is validated that the scrubbing does happen every minute. IF a scrub run takes longer than a minute to complete, then it waits for the run to complete and then schedules the next run after a minute. Moving this BZ to verified in 3.2
Setting the qe_test_coverage to '-' for the following reasons: * This option is introduced purely for testing purpose * It is going to phase out in the coming releases as we have introduced 'scrub ondemand' option
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0486.html