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

Clearifies the --pre-hash option.

Browse source
This commit is contained in:
Andrea Mazzoleni 2014-09-21 22:28:36 +02:00
parent 605e7da478
commit 3df3265e9e
3 changed files with 27 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

19
snapraid.1
View file

@ -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.

19
snapraid.d
View file

@ -518,16 +518,15 @@ Options
-h, --pre-hash
In the "sync" 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 "sync" 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 "sync" 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 "pre-hash" mode and have
all the data hashed two times to ensure its integrity.
This option can be used only with the "sync" command.

19
snapraid.txt
View file

@ -563,16 +563,15 @@ SnapRAID provides the following options:
-h, --pre-hash
In the "sync" 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 "sync" 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 "sync" 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 "pre-hash" mode and have
all the data hashed two times to ensure its integrity.
This option can be used only with the "sync" command.