Restore defalt scrub percentage to 8%

This is like the previous 8.1 version, even if the documented
one in the doc was 12%, the real one was 1/12==8%.
This commit is contained in:
Andrea Mazzoleni 2015-11-12 23:04:49 +01:00
parent 54c91ec440
commit fa3f17ac20
4 changed files with 11 additions and 11 deletions

View file

@ -623,8 +623,8 @@ int state_scrub(struct snapraid_state* state, int plan, int olderthan)
if (plan >= 0) {
countlimit = md(blockmax, plan, 100);
} else {
/* by default scrub 12.5% of the array (100/8=12.5) */
countlimit = md(blockmax, 1, 8);
/* by default scrub 8.33% of the array (100/12=8.(3)) */
countlimit = md(blockmax, 1, 12);
}
if (olderthan >= 0) {

View file

@ -307,7 +307,7 @@ snapraid scrub
This command verifies the data in your array comparing it with
the hash computed in the \[dq]sync\[dq] command.
.PP
Every run of the command checks the 12.5% of the array, but not data
Every run of the command checks about the 8% of the array, but not data
already scrubbed in the previous 10 days.
You can use the \-p, \-\-plan option to specify a different amount,
and the \-o, \-\-older\-than option to specify a different age in days.
@ -778,10 +778,10 @@ The files in the array are NOT modified.
Scrubs the array, checking for silent or input/output errors in data
and parity disks.
.PP
For each command invocation, the 12.5% of the array is checked, but
For each command invocation, about the 8% of the array is checked, but
nothing that was already scrubbed in the last 10 days.
This means that scrubbing once a week, every bit of data is checked
at least one time every two months.
at least one time every three months.
.PP
You can define a different scrub plan or amount using the \-p, \-\-plan
option that takes as argument:

View file

@ -171,7 +171,7 @@ Getting Started
This command verifies the data in your array comparing it with
the hash computed in the "sync" command.
Every run of the command checks the 12.5% of the array, but not data
Every run of the command checks about the 8% of the array, but not data
already scrubbed in the previous 10 days.
You can use the -p, --plan option to specify a different amount,
and the -o, --older-than option to specify a different age in days.
@ -486,10 +486,10 @@ Commands
Scrubs the array, checking for silent or input/output errors in data
and parity disks.
For each command invocation, the 12.5% of the array is checked, but
For each command invocation, about the 8% of the array is checked, but
nothing that was already scrubbed in the last 10 days.
This means that scrubbing once a week, every bit of data is checked
at least one time every two months.
at least one time every three months.
You can define a different scrub plan or amount using the -p, --plan
option that takes as argument:

View file

@ -186,7 +186,7 @@ run the "scrub" command.
This command verifies the data in your array comparing it with
the hash computed in the "sync" command.
Every run of the command checks the 12.5% of the array, but not data
Every run of the command checks about the 8% of the array, but not data
already scrubbed in the previous 10 days.
You can use the -p, --plan option to specify a different amount,
and the -o, --older-than option to specify a different age in days.
@ -524,10 +524,10 @@ The files in the array are NOT modified.
Scrubs the array, checking for silent or input/output errors in data
and parity disks.
For each command invocation, the 12.5% of the array is checked, but
For each command invocation, about the 8% of the array is checked, but
nothing that was already scrubbed in the last 10 days.
This means that scrubbing once a week, every bit of data is checked
at least one time every two months.
at least one time every three months.
You can define a different scrub plan or amount using the -p, --plan
option that takes as argument: