mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 19:01:57 -04:00
Reviews docs for the new -F option.
This commit is contained in:
parent
05b17e5f0b
commit
fb4f257593
4 changed files with 13 additions and 12 deletions
4
HISTORY
4
HISTORY
|
|
@ -7,6 +7,10 @@ SnapRAID HISTORY
|
|||
"sync" commands without it.
|
||||
* When saving the content file keep a copy of the previos one adding
|
||||
the ".backup" extension.
|
||||
* Added a new -F, --force-full option that forces a full sync reusing
|
||||
the hash data present in the content file.
|
||||
This may be useful when using an old content file like the backup
|
||||
one.
|
||||
* Auto exclude the lock file.
|
||||
* Don't prints the 'UUID set' message anymore because it's the normal
|
||||
condition for empty disks.
|
||||
|
|
|
|||
|
|
@ -836,12 +836,11 @@ This option can be used only with the \[dq]sync\[dq] command.
|
|||
.B \-F, \-\-force\-full
|
||||
In the \[dq]sync\[dq] command, forces a full rebuild of the parity.
|
||||
This option can be used when you reverted back to an old content
|
||||
file, because you have lost the most recent one, and you still have
|
||||
the parity data.
|
||||
file, like the backup one, and you still have the parity data.
|
||||
Instead of recomputing the parity from scratch, this allows
|
||||
to reuse the hashes present in the content file to validate data,
|
||||
and to maintain data protection using the old content file and the
|
||||
parity data you have.
|
||||
and to maintain data protection during the \[dq]sync\[dq] process using
|
||||
the old content file and the parity data you have.
|
||||
This option can be used only with the \[dq]sync\[dq] command.
|
||||
.TP
|
||||
.B \-l, \-\-log FILE
|
||||
|
|
|
|||
|
|
@ -599,12 +599,11 @@ Options
|
|||
-F, --force-full
|
||||
In the "sync" command, forces a full rebuild of the parity.
|
||||
This option can be used when you reverted back to an old content
|
||||
file, because you have lost the most recent one, and you still have
|
||||
the parity data.
|
||||
file, like the backup one, and you still have the parity data.
|
||||
Instead of recomputing the parity from scratch, this allows
|
||||
to reuse the hashes present in the content file to validate data,
|
||||
and to maintain data protection using the old content file and the
|
||||
parity data you have.
|
||||
and to maintain data protection during the "sync" process using
|
||||
the old content file and the parity data you have.
|
||||
This option can be used only with the "sync" command.
|
||||
|
||||
-l, --log FILE
|
||||
|
|
|
|||
|
|
@ -644,12 +644,11 @@ SnapRAID provides the following options:
|
|||
-F, --force-full
|
||||
In the "sync" command, forces a full rebuild of the parity.
|
||||
This option can be used when you reverted back to an old content
|
||||
file, because you have lost the most recent one, and you still have
|
||||
the parity data.
|
||||
file, like the backup one, and you still have the parity data.
|
||||
Instead of recomputing the parity from scratch, this allows
|
||||
to reuse the hashes present in the content file to validate data,
|
||||
and to maintain data protection using the old content file and the
|
||||
parity data you have.
|
||||
and to maintain data protection during the "sync" process using
|
||||
the old content file and the parity data you have.
|
||||
This option can be used only with the "sync" command.
|
||||
|
||||
-l, --log FILE
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue