mirror of
https://github.com/amadvance/snapraid.git
synced 2026-11-21 23:46:27 -05:00
Clearifies the --pre-hash option.
This commit is contained in:
parent
605e7da478
commit
3df3265e9e
3 changed files with 27 additions and 30 deletions
19
snapraid.1
19
snapraid.1
|
|
@ -755,16 +755,15 @@ This option can be used only with the \[dq]check\[dq] command.
|
|||
.TP
|
||||
.B \-h, \-\-pre\-hash
|
||||
In the \[dq]sync\[dq] command run a preliminary hashing phase of all
|
||||
the new data to ensure that during the parity computation
|
||||
the data read is correct.
|
||||
Normally in \[dq]sync\[dq] no preliminary hashing is done, and the new
|
||||
data is hashed directly during the parity computation when it\'s
|
||||
read for the first time,
|
||||
This happens when the system is under heavy pressure due all
|
||||
disks spinning and CPU busy, and in such extreme conditions,
|
||||
if your machine has a latent hardware problem, it\'s possible to
|
||||
encounter silent errors what cannot be detected because the data
|
||||
is not yet hashed.
|
||||
the new data to verify the data used in the parity computation.
|
||||
Usually in \[dq]sync\[dq] no preliminary hashing is done, and the new
|
||||
data is hashed just before the parity computation when it\'s read
|
||||
for the first time,
|
||||
Unfortunately, this process happens when the system is under
|
||||
heavy load, with all disks spinning and a busy CPU.
|
||||
This is an extreme condition for your machine, and if it has a
|
||||
latent hardware problem, it\'s possible to encounter silent errors
|
||||
what cannot be detected because the data is not yet hashed.
|
||||
To avoid this risk, you can enable the \[dq]pre\-hash\[dq] mode and have
|
||||
all the data hashed two times to ensure its integrity.
|
||||
This option can be used only with the \[dq]sync\[dq] command.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue