rt/snapraid
1
0
Fork 0
mirror of https://github.com/amadvance/snapraid.git synced 2026-10-25 18:40:19 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

More clear doc.

Browse source
This commit is contained in:
Andrea Mazzoleni 2013-09-10 21:22:06 +02:00
parent d01c480af4
commit 7ca7225922
3 changed files with 18 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

11
snapraid.1
View file

@ -331,11 +331,12 @@ snapraid scrub
.PD
.RE
.PP
As difference than \(a"check\(a" this command verifies only the oldest data
This command is similar at \(a"check\(a" but verifies only the oldest data
in your array. Every run of the command checks about 12% of the data,
but nothing newer than 10 days.
You can use the \(hyp, \(hy\(hypercentage option to specify a different amount,
and the \(hyo, \(hy\(hyolder\(hythan option to specify a different age in days:
and the \(hyo, \(hy\(hyolder\(hythan option to specify a different age in days.
For example, to check 5% of the array older than 20 days use:
.PP
.RS 4
snapraid \(hyp 5 \(hyo 20 scrub
@ -345,7 +346,7 @@ snapraid \(hyp 5 \(hyo 20 scrub
.RE
.PP
If silent errors are found, the corresponding blocks are marked as bad
in the \(a"concent\(a" file, and listed in the \(a"status\(a" command.
in the \(a"content\(a" file, and listed in the \(a"status\(a" command.
.PP
.RS 4
snapraid status
@ -364,8 +365,8 @@ snapraid \(hye fix
.PD
.RE
.PP
and at the next \(a"scrub\(a" the errors will disappear from the \(a"status\(a"
report. You can use \(hyp 0 to scrub only them.
At the next \(a"scrub\(a" the errors will disappear from the \(a"status\(a" report
if really fixed. You can use \(hyp 0 to scrub only blocks marked as bad.
.PP
.RS 4
snapraid \(hyp 0 scrub

11
snapraid.d
View file

@ -184,16 +184,17 @@ Getting Started
:snapraid scrub
As difference than "check" this command verifies only the oldest data
This command is similar at "check" but verifies only the oldest data
in your array. Every run of the command checks about 12% of the data,
but nothing newer than 10 days.
You can use the -p, --percentage option to specify a different amount,
and the -o, --older-than option to specify a different age in days:
and the -o, --older-than option to specify a different age in days.
For example, to check 5% of the array older than 20 days use:
:snapraid -p 5 -o 20 scrub
If silent errors are found, the corresponding blocks are marked as bad
in the "concent" file, and listed in the "status" command.
in the "content" file, and listed in the "status" command.
:snapraid status
@ -202,8 +203,8 @@ Getting Started
:snapraid -e fix
and at the next "scrub" the errors will disappear from the "status"
report. You can use -p 0 to scrub only them.
At the next "scrub" the errors will disappear from the "status" report
if really fixed. You can use -p 0 to scrub only blocks marked as bad.
:snapraid -p 0 scrub

11
snapraid.txt
View file

@ -201,16 +201,17 @@ command.
snapraid scrub
As difference than "check" this command verifies only the oldest data
This command is similar at "check" but verifies only the oldest data
in your array. Every run of the command checks about 12% of the data,
but nothing newer than 10 days.
You can use the -p, --percentage option to specify a different amount,
and the -o, --older-than option to specify a different age in days:
and the -o, --older-than option to specify a different age in days.
For example, to check 5% of the array older than 20 days use:
snapraid -p 5 -o 20 scrub
If silent errors are found, the corresponding blocks are marked as bad
in the "concent" file, and listed in the "status" command.
in the "content" file, and listed in the "status" command.
snapraid status
@ -219,8 +220,8 @@ containing bad blocks:
snapraid -e fix
and at the next "scrub" the errors will disappear from the "status"
report. You can use -p 0 to scrub only them.
At the next "scrub" the errors will disappear from the "status" report
if really fixed. You can use -p 0 to scrub only blocks marked as bad.
snapraid -p 0 scrub