From 3df3265e9ebee8708f165c2e23fba059d012a185 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Sun, 21 Sep 2014 22:28:36 +0200 Subject: [PATCH] Clearifies the --pre-hash option. --- snapraid.1 | 19 +++++++++---------- snapraid.d | 19 +++++++++---------- snapraid.txt | 19 +++++++++---------- 3 files changed, 27 insertions(+), 30 deletions(-) diff --git a/snapraid.1 b/snapraid.1 index f1a0a6fc..a635197d 100644 --- a/snapraid.1 +++ b/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. diff --git a/snapraid.d b/snapraid.d index 6dc1c421..176b463f 100644 --- a/snapraid.d +++ b/snapraid.d @@ -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. diff --git a/snapraid.txt b/snapraid.txt index ed4ed464..5109a019 100644 --- a/snapraid.txt +++ b/snapraid.txt @@ -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.