mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 19:01:57 -04:00
Clearify the search process done by fix in the doc
This commit is contained in:
parent
ae2171570b
commit
9f263b6fa8
3 changed files with 45 additions and 21 deletions
22
snapraid.1
22
snapraid.1
|
|
@ -764,9 +764,9 @@ size and timestamp.
|
|||
If the file size or timestamp are different, the parity data
|
||||
is recomputed for the whole file.
|
||||
If the file is moved or renamed in the same disk, keeping the
|
||||
same inode, the parity is no recomputed.
|
||||
same inode, the parity is not recomputed.
|
||||
If the file is moved to another disk, the parity is recomputed,
|
||||
but the previously compute hash information is kept.
|
||||
but the previously computed hash information is kept.
|
||||
.PP
|
||||
The \[dq]content\[dq] and \[dq]parity\[dq] files are modified if necessary.
|
||||
The files in the array are NOT modified.
|
||||
|
|
@ -826,19 +826,27 @@ All the files and the parity data are compared with the snapshot
|
|||
state saved in the last \[dq]sync\[dq].
|
||||
If a difference is found, it\'s reverted to the stored snapshot.
|
||||
.PP
|
||||
Note that \[dq]fix\[dq] doesn\'t differentiate between errors and intentional
|
||||
modifications. It unconditionally reverts the file state at the last \[dq]sync\[dq].
|
||||
The \[dq]fix\[dq] command doesn\'t differentiate between errors and
|
||||
intentional modifications. It unconditionally reverts the file state
|
||||
at the last \[dq]sync\[dq].
|
||||
.PP
|
||||
If no other option is specified the full array is processed.
|
||||
Use the filter options to select a subset of files or disks to operate on.
|
||||
.PP
|
||||
To only fix the blocks marked bad during \[dq]sync\[dq] and \[dq]scrub\[dq],
|
||||
use the \-e, \-\-filter\-error option.
|
||||
As difference from other filter options, with this one fixes are
|
||||
As difference from other filter options, with this one the fixes are
|
||||
applied only to files that are not modified from the the latest \[dq]sync\[dq].
|
||||
.PP
|
||||
All the files that cannot be fixed are renamed adding
|
||||
the \[dq].unrecoverable\[dq] extension.
|
||||
All the files that cannot be fixed are renamed adding the
|
||||
\[dq].unrecoverable\[dq] extension.
|
||||
.PP
|
||||
Before fixing, the full array is scanned to find any moved file,
|
||||
after the last \[dq]sync\[dq] operation.
|
||||
These files are identified by their timestamp, ignoring their name
|
||||
and directory, and are used in the recovering process if necessary.
|
||||
If you moved some of them outside the array, you can use the \-i, \-\-import
|
||||
option to specify additional directories to scan.
|
||||
.PP
|
||||
Files are identified only by path, and not by inode.
|
||||
.PP
|
||||
|
|
|
|||
22
snapraid.d
22
snapraid.d
|
|
@ -471,9 +471,9 @@ Commands
|
|||
If the file size or timestamp are different, the parity data
|
||||
is recomputed for the whole file.
|
||||
If the file is moved or renamed in the same disk, keeping the
|
||||
same inode, the parity is no recomputed.
|
||||
same inode, the parity is not recomputed.
|
||||
If the file is moved to another disk, the parity is recomputed,
|
||||
but the previously compute hash information is kept.
|
||||
but the previously computed hash information is kept.
|
||||
|
||||
The "content" and "parity" files are modified if necessary.
|
||||
The files in the array are NOT modified.
|
||||
|
|
@ -531,19 +531,27 @@ Commands
|
|||
state saved in the last "sync".
|
||||
If a difference is found, it's reverted to the stored snapshot.
|
||||
|
||||
Note that "fix" doesn't differentiate between errors and intentional
|
||||
modifications. It unconditionally reverts the file state at the last "sync".
|
||||
The "fix" command doesn't differentiate between errors and
|
||||
intentional modifications. It unconditionally reverts the file state
|
||||
at the last "sync".
|
||||
|
||||
If no other option is specified the full array is processed.
|
||||
Use the filter options to select a subset of files or disks to operate on.
|
||||
|
||||
To only fix the blocks marked bad during "sync" and "scrub",
|
||||
use the -e, --filter-error option.
|
||||
As difference from other filter options, with this one fixes are
|
||||
As difference from other filter options, with this one the fixes are
|
||||
applied only to files that are not modified from the the latest "sync".
|
||||
|
||||
All the files that cannot be fixed are renamed adding
|
||||
the ".unrecoverable" extension.
|
||||
All the files that cannot be fixed are renamed adding the
|
||||
".unrecoverable" extension.
|
||||
|
||||
Before fixing, the full array is scanned to find any moved file,
|
||||
after the last "sync" operation.
|
||||
These files are identified by their timestamp, ignoring their name
|
||||
and directory, and are used in the recovering process if necessary.
|
||||
If you moved some of them outside the array, you can use the -i, --import
|
||||
option to specify additional directories to scan.
|
||||
|
||||
Files are identified only by path, and not by inode.
|
||||
|
||||
|
|
|
|||
22
snapraid.txt
22
snapraid.txt
|
|
@ -507,9 +507,9 @@ size and timestamp.
|
|||
If the file size or timestamp are different, the parity data
|
||||
is recomputed for the whole file.
|
||||
If the file is moved or renamed in the same disk, keeping the
|
||||
same inode, the parity is no recomputed.
|
||||
same inode, the parity is not recomputed.
|
||||
If the file is moved to another disk, the parity is recomputed,
|
||||
but the previously compute hash information is kept.
|
||||
but the previously computed hash information is kept.
|
||||
|
||||
The "content" and "parity" files are modified if necessary.
|
||||
The files in the array are NOT modified.
|
||||
|
|
@ -571,19 +571,27 @@ All the files and the parity data are compared with the snapshot
|
|||
state saved in the last "sync".
|
||||
If a difference is found, it's reverted to the stored snapshot.
|
||||
|
||||
Note that "fix" doesn't differentiate between errors and intentional
|
||||
modifications. It unconditionally reverts the file state at the last "sync".
|
||||
The "fix" command doesn't differentiate between errors and
|
||||
intentional modifications. It unconditionally reverts the file state
|
||||
at the last "sync".
|
||||
|
||||
If no other option is specified the full array is processed.
|
||||
Use the filter options to select a subset of files or disks to operate on.
|
||||
|
||||
To only fix the blocks marked bad during "sync" and "scrub",
|
||||
use the -e, --filter-error option.
|
||||
As difference from other filter options, with this one fixes are
|
||||
As difference from other filter options, with this one the fixes are
|
||||
applied only to files that are not modified from the the latest "sync".
|
||||
|
||||
All the files that cannot be fixed are renamed adding
|
||||
the ".unrecoverable" extension.
|
||||
All the files that cannot be fixed are renamed adding the
|
||||
".unrecoverable" extension.
|
||||
|
||||
Before fixing, the full array is scanned to find any moved file,
|
||||
after the last "sync" operation.
|
||||
These files are identified by their timestamp, ignoring their name
|
||||
and directory, and are used in the recovering process if necessary.
|
||||
If you moved some of them outside the array, you can use the -i, --import
|
||||
option to specify additional directories to scan.
|
||||
|
||||
Files are identified only by path, and not by inode.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue