[Bugs] [Bug 1355635] New: [Bitrot]: Scrub status- Certain fields continue to show previous run's details, even if the current run is in progress

[bugzilla at redhat.com]

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

            Bug ID: 1355635
           Summary: [Bitrot]: Scrub status- Certain fields continue to
                    show previous run's details, even if the current run
                    is in progress
           Product: GlusterFS
           Version: 3.7.13
         Component: bitrot
          Keywords: ZStream
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: bugs at gluster.org, rhs-bugs at redhat.com,
                    rmekala at redhat.com, sanandpa at redhat.com
        Depends On: 1337444, 1352871
      Docs Contact: bugs at gluster.org



+++ This bug was initially created as a clone of Bug #1352871 +++

+++ This bug was initially created as a clone of Bug #1337444 +++

Description of problem:
========================

In scenarios where scrubber would take more time to finish scrubbing files, a
'scrub status' output when scrubbing is in progress, displays the previous
run's information for 'last completed scrub time' and 'duration of last scrub'.
This provides an incorrect view to the user, giving the impression that
scrubbing has completed. We should ideally have the field 'State of scrub' set
to 'In progress' and the above mentioned fields set to '-' . The other two
fields (files scrubbed, files skipped) correctly show the present run's
details.


Version-Release number of selected component (if applicable):
=============================================================

How reproducible:
================
Always


Steps to Reproduce:
====================

1. Have a 4node cluster, with a dist-rep volume and sharding enabled. Set the
scrub frequency to 'hourly'
2. Create 100 1MB files and wait for the scrubber to finish its run.
3. View the scrub status output for the validity of the fields that it shows.
4. Create 5 4GB files and wait for the next run of scrubbing to start. 
5. When the scrubbing is in progress (as seen from scrub.log), issue a 'gluster
volume bitrot <volname> scrub status'

Actual results:
===============
Scrub status shows 4 fields with respect to every node. 2 fields are updated as
per the current run, and 2 as per the previous run.


Expected results:
=================
Either all the 4 fields must reflect the current run, OR all 4 fields must
reflect the previous run. Preferable would be to let the user know that
scrubbing is in progress, and update the fields accordingly.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1337444
[Bug 1337444] [Bitrot]: Scrub status- Certain fields continue to show
previous run's details, even if the current run is in progress
https://bugzilla.redhat.com/show_bug.cgi?id=1352871
[Bug 1352871] [Bitrot]: Scrub status- Certain fields continue to show
previous run's details, even if the current run is in progress
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.