Description of problem: ----------------------- The manual page of gluster should be updated with respect to gluster bitrot scrub-frequency option. Scrub-frequency on hourly basis is supported but not mentioned in the man page. Version-Release number of selected component (if applicable): ------------------------------------------------------------- glusterfs-3.8.4-48.el7rhgs.x86_64 How reproducible: ----------------- always Steps to Reproduce: ------------------- 1. man gluster Actual results: --------------- volume bitrot <VOLNAME> scrub-frequency {daily|weekly|biweekly|monthly} Expected results: ----------------- volume bitrot <VOLNAME> scrub-frequency {hourly|daily|weekly|biweekly|monthly}
This was intentional and only for testing purpose. Hence not advertised in man page. Closing this bug as not a bug.
If I remember correctly, it was only 'minute' that was introduced for testing purpose - and that is why we don't have a mention, either in man page, or in 'gluster volume bitrot -h'. 'Hourly' is mentioned in 'gluster volume bitrot -h', but NOT in man page. I don't think we should have this discrepancy there..
You are right. I got confused with hour. It was minute. Re-opening it and will be addressed.
Upstream Patch: https://review.gluster.org/18545
(In reply to Kotresh HR from comment #5) > Upstream Patch: > > https://review.gluster.org/18545 That was merged almost a year ago. What's the latest status?
(In reply to Yaniv Kaul from comment #7) > (In reply to Kotresh HR from comment #5) > > Upstream Patch: > > > > https://review.gluster.org/18545 > > That was merged almost a year ago. What's the latest status? It will be part of next downstream release. 3.4 was out of planning exit phase, when this was merged. So didn't allow this as this didn't come into blocker criteria. Thanks, Kotresh HR
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://access.redhat.com/errata/RHEA-2019:3249