+++ This bug was initially created as a clone of Bug #1231024 +++ +++ This bug was initially created as a clone of Bug #1225747 +++ Description of problem: ========================== scrub frequecny and throttle change information need to be present in Scrubber log Version-Release number of selected component (if applicable): ==================== scrub frequecny and throttle change information need to be present in Scrubber log How reproducible: Steps to Reproduce: ===================== 1.Create a volume and enable bitrot 2.Change the Scrubber frequency and throttle values but we are not logging this information in the log 3. Actual results: Expected results: ==================== It would be good to log this information in the log for tracking and troubleshooting purpose
REVIEW: http://review.gluster.org/11190 (features/bitrot: log scrub frequency & throttle values) posted (#3) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11190 (features/bitrot: log scrub frequency & throttle values) posted (#4) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11190 (features/bitrot: log scrub frequency & throttle values) posted (#5) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11190 (features/bitrot: log scrub frequency & throttle values) posted (#6) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11263 (Revert "tests/bitrot: Induce delay before invoking bitrot subcommands") posted (#2) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11190 (features/bitrot: log scrub frequency & throttle values) posted (#8) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11190 (features/bitrot: log scrub frequency & throttle values) posted (#9) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11190 (features/bitrot: log scrub frequency & throttle values) posted (#10) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11190 (features/bitrot: log scrub frequency & throttle values) posted (#11) for review on master 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.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