diff options
| author | Kotresh HR <khiremat@redhat.com> | 2017-06-15 08:31:06 -0400 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2017-06-16 06:01:49 +0000 |
| commit | f0fb166078d59cab2a33583591b6448326247c40 (patch) | |
| tree | 7b5257b04d2c5ea69f08e0a6a1c9b1751dc7b30f /glusterfsd | |
| parent | b9fb7ea63d6120faaeb75ffa0cafbc0ab0e4a619 (diff) | |
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@redhat.com>
Reviewed-on: https://review.gluster.org/17552
Smoke: Gluster Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Diffstat (limited to 'glusterfsd')
0 files changed, 0 insertions, 0 deletions