[Bugs] [Bug 1462080] [Bitrot]: Inconsistency seen with 'scrub ondemand' - fails to trigger scrub

[bugzilla at redhat.com]

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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17553 committed in release-3.10 by
Raghavendra Talur (rtalur at redhat.com) 
------
commit 8f8850ae8c7fd64db01ec19bfeb6ef4bd1911bd8
Author: Kotresh HR <khiremat at redhat.com>
Date:   Thu Jun 15 08:31:06 2017 -0400

    feature/bitrot: Fix ondemand scrub

    The flag which keeps tracks of whether the scrub
    frequency is changed from previous value should
    not be considered for on-demand scrubbing. It
    should be considered only for 'scrub-frequency'
    where it should not be re-scheduled if it is
    set to same value again. But in case ondemand
    scrub, it should start the scrub immediately
    no matter what the scrub-frequency.

    Reproducer:
    1. Enable bitrot
    2. Set scrub-throttle
    3. Set ondemand scrub
    Make sure glusterd is not restarted while doing
    below steps

    > Change-Id: Ice5feaece7fff1579fb009d1a59d2b8292e23e0b
    > BUG: 1461845
    > Signed-off-by: Kotresh HR <khiremat at redhat.com>
    > Reviewed-on: https://review.gluster.org/17552
    > Smoke: Gluster Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>
    > NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    (cherry picked from commit f0fb166078d59cab2a33583591b6448326247c40)

    Change-Id: Ice5feaece7fff1579fb009d1a59d2b8292e23e0b
    BUG: 1462080
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: https://review.gluster.org/17553
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur at redhat.com>

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