Some manual changes about -e use

This commit is contained in:
Andrea Mazzoleni 2015-07-19 08:21:21 +02:00
parent e2d5ab575d
commit 780dae75ff
3 changed files with 12 additions and 0 deletions

View file

@ -667,6 +667,9 @@ errors encountered while scrubbing.
Note that the information presented refers at the latest time you
run \[dq]sync\[dq]. Later modifications are not taken into account.
.PP
If bad blocks were detected, their block numbers are listed.
To fix them, you can use the \[dq]fix \-e\[dq] command.
.PP
Nothing is modified.
.SS smart
Prints a SMART report of all the disks of the array.
@ -783,6 +786,7 @@ are marked as bad in the \[dq]content\[dq] file.
These bad blocks are listed in \[dq]status\[dq], and can be fixed with \[dq]fix \-e\[dq].
After the fix, at the next scrub they will be rechecked, and if found
corrected, the bad mark will be removed.
To scrub only the bad blocks, you can use the \[dq]scrub \-p 0\[dq] command.
.PP
It\'s recommended to run \[dq]scrub\[dq] on a synced array, to avoid to have
reported error caused by unsynced data. These errors are recognized

View file

@ -385,6 +385,9 @@ Commands
Note that the information presented refers at the latest time you
run "sync". Later modifications are not taken into account.
If bad blocks were detected, their block numbers are listed.
To fix them, you can use the "fix -e" command.
Nothing is modified.
smart
@ -492,6 +495,7 @@ Commands
These bad blocks are listed in "status", and can be fixed with "fix -e".
After the fix, at the next scrub they will be rechecked, and if found
corrected, the bad mark will be removed.
To scrub only the bad blocks, you can use the "scrub -p 0" command.
It's recommended to run "scrub" on a synced array, to avoid to have
reported error caused by unsynced data. These errors are recognized

View file

@ -411,6 +411,9 @@ errors encountered while scrubbing.
Note that the information presented refers at the latest time you
run "sync". Later modifications are not taken into account.
If bad blocks were detected, their block numbers are listed.
To fix them, you can use the "fix -e" command.
Nothing is modified.
5.2 smart
@ -530,6 +533,7 @@ are marked as bad in the "content" file.
These bad blocks are listed in "status", and can be fixed with "fix -e".
After the fix, at the next scrub they will be rechecked, and if found
corrected, the bad mark will be removed.
To scrub only the bad blocks, you can use the "scrub -p 0" command.
It's recommended to run "scrub" on a synced array, to avoid to have
reported error caused by unsynced data. These errors are recognized