Patch posted Upstream: http://review.gluster.org/#/c/14044/
Upstream Patches: master: https://review.gluster.org/#/c/14044/ https://review.gluster.org/#/c/14120/ https://review.gluster.org/#/c/14121/ release-3.7: https://review.gluster.org/#/c/14140/ https://review.gluster.org/#/c/14141/ https://review.gluster.org/#/c/14142/ Downstream Patches: https://code.engineering.redhat.com/gerrit/73573/ https://code.engineering.redhat.com/gerrit/73574/ https://code.engineering.redhat.com/gerrit/#/c/73579/
Tested and verified this on the build 3.7.9-6. Have raised new BZs for issues found regarding scrub status output. Thus, moving this blanket-BZ to verified in 3.1.3.
Laura, ---- When users ran 'gluster volume bitrot $volname scrub status', several statistics were reported as zeroes. The following statistics now display correctly: number of scrubbed files, number of unsigned files, last completed scrub time, and duration of last scrub. ---- The above doc text says, several statistics were reported as zeroes. But since they were reporting zeroes, we had masked them not to show in previous release. So the following fields were not being shown at all in previous release. number of scrubbed files, number of unsigned files, last completed scrub time, and duration of last scrub. Now we show them with accurate values. So the correction would be to say. ------- When users ran 'gluster volume bitrot $volname scrub status', the following additional statistics would be displayed: number of scrubbed files, number of unsigned files, last completed scrub time, and duration of last scrub. -------
Doc Text looks fine to me.
Hi Laura, Could you please change the the field 'number of unsigned files' to 'number of skipped files' ? That is how it actually gets shown in the scrub status output. Have pasted a sample output below for your reference. [root@dhcp47-188 ~]# gluster v bitrot disp scrub status Volume name : disp State of scrub: Active Scrub impact: lazy Scrub frequency: hourly Bitrot error log location: /var/log/glusterfs/bitd.log Scrubber error log location: /var/log/glusterfs/scrub.log ========================================================= Node: localhost Number of Scrubbed files: 22 Number of Skipped files: 0 Last completed scrub time: 2016-06-05 10:53:58 Duration of last scrub (D:M:H:M:S): 0:0:0:14 Error count: 0 ========================================================= Node: 10.70.46.193 Number of Scrubbed files: 0 Number of Skipped files: 0 Last completed scrub time: Scrubber pending to complete. Duration of last scrub (D:M:H:M:S): 0:0:0:0 Error count: 0 ========================================================= Node: 10.70.46.215 Number of Scrubbed files: 22 Number of Skipped files: 0 Last completed scrub time: 2016-06-05 10:56:57 Duration of last scrub (D:M:H:M:S): 0:0:0:13 Error count: 0 ========================================================= Node: 10.70.46.187 Number of Scrubbed files: 22 Number of Skipped files: 0 Last completed scrub time: 2016-06-05 10:57:03 Duration of last scrub (D:M:H:M:S): 0:0:0:13 Error count: 0 ========================================================= [root@dhcp47-188 ~]#
Please do acknowledge. Thanks.
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/RHBA-2016:1240