[Bugs] [Bug 1207627] BitRot :- Data scrubbing status is not available

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1207627



--- Comment #21 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/10231 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 097e131481d25e5b1f859f4ea556b8bf56155472
Author: Gaurav Kumar Garg <ggarg at redhat.com>
Date:   Wed Mar 25 18:07:24 2015 +0530

    glusterd: cli command implementation for bitrot scrub status

    CLI command  for bitrot scrub status will be :

    gluster volume bitrot <volname> scrub status

    Above command will show the statistics of bitrot scrubber.

    Upon execution of this command it will show some common
    scrubber tunable value of volume <VOLNAME> followed by
    statistics of scrubber statistics of individual nodes.

    sample ouput for single node:

    Volume name : <VOLNAME>

    State of scrub: Active

    Scrub frequency: biweekly

    Bitrot error log location: /var/log/glusterfs/bitd.log

    Scrubber error log location: /var/log/glusterfs/scrub.log

    =========================================================

    Node name:

    Number of Scrubbed files:

    Number of Unsigned files:

    Last completed scrub time:

    Duration of last scrub:

    Error count:

    =========================================================

    This is just infrastructure. list of bad file, last scrub
    time, error count value will be taken care by
    http://review.gluster.org/#/c/12503/  and
    http://review.gluster.org/#/c/12654/ patches.

    Change-Id: I3ed3c7057c9d0c894233f4079a7f185d90c202d1
    BUG: 1207627
    Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>
    Reviewed-on: http://review.gluster.org/10231
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the Docs Contact for the bug.