diff --git a/snapraid.1 b/snapraid.1 index 915df9cb..0fb9b7b1 100644 --- a/snapraid.1 +++ b/snapraid.1 @@ -647,7 +647,7 @@ and ignore all the parity data. This command will take a long time, but if you are not paranoid, you can skip it. .SS STEP 4 \-> Sync -Run the \[dq]sync\[dq] command to resynchronize the array with the new disk. +Run the \[dq]sync\[dq] command to re\-synchronize the array with the new disk. .PP .RS 4 snapraid sync @@ -745,7 +745,7 @@ Spins up all the disks of the array. .PP You can spin\-up only some specific disks using the \-d, \-\-filter\-disk option. .PP -Take care that spinniup\-up all the disks at the same time needs a lot of power. +Take care that spinning\-up all the disks at the same time needs a lot of power. Ensure that your power\-supply can sustain that. .PP Nothing is modified. @@ -912,7 +912,7 @@ Verify all the files and the parity data. It works like \[dq]fix\[dq], but it only simulates a recovery and no change is written in the array. .PP -This command is mostly intended for manual verifications, +This command is mostly intended for manual verification, like after a recovery process or in other special conditions. For periodic and scheduled checks uses \[dq]scrub\[dq]. .PP @@ -931,7 +931,7 @@ Nothing is modified. .SS dup Lists all the duplicate files. Two files are assumed equal if their hashes are matching. The file data is not read, but only the -precomputed hashes are used. +pre\-computed hashes are used. .PP Nothing is modified. .SS pool @@ -942,7 +942,7 @@ The files are not really copied here, but just linked using symbolic links. .PP When updating, all the present symbolic links and empty -subdirectories are deleted and replaced with the new +sub\-directories are deleted and replaced with the new view of the array. Any other regular file is left in place. .PP Nothing is modified outside the pool directory. @@ -962,20 +962,20 @@ low level devices used by a single disk in the array. .PP Nothing is modified. .SS touch -Sets arbitrarely the sub\-second timestamp of all the files +Sets arbitrarily the sub\-second time\-stamp of all the files that have it at zero. .PP This improves the SnapRAID capability to recognize moved -and copied files as it makes the timestamp almost unique, +and copied files as it makes the time\-stamp almost unique, removing possible duplicates. .PP -More specifically, if the sub\-second timestamp is not zero, +More specifically, if the sub\-second time\-stamp is not zero, a moved or copied file is identified as such if it matches -the name, size and timestamp. If instead the sub\-second timestamp +the name, size and time\-stamp. If instead the sub\-second time\-stamp is zero, it\'s considered a copy only if it matches the full path, -size and timestamp. +size and time\-stamp. .PP -Note that the second precision timestamp is not modified, +Note that the second precision time\-stamp is not modified, and all the dates and times of your files will be maintained. .SS rehash Schedules a rehash of the whole array. @@ -1090,7 +1090,7 @@ Imports from the specified directory any file that you deleted from the array after the last \[dq]sync\[dq]. If you still have such files, they could be used by \[dq]check\[dq] and \[dq]fix\[dq] to improve the recover process. -The files are read also in subdirectories and they are +The files are read also in sub\-directories and they are identified regardless of their name. This option can be used only with \[dq]check\[dq] and \[dq]fix\[dq]. .TP @@ -1146,7 +1146,7 @@ This allows to identify copied or moved files from one disk to another, and to reuse the already computed hash information to detect silent errors or to recover missing files. This behavior, in some rare cases, may result in false positives, -or in a slow process due the many hash verifications, and this +or in a slow process due the many hash verification, and this option allows to resolve them. This option can be used only with \[dq]sync\[dq], \[dq]check\[dq] and \[dq]fix\[dq]. .TP @@ -1280,7 +1280,7 @@ is enabled: 6\-parity enables hexa (six) parity .PD .PP -Each parity level requires the precence of all the previous parity +Each parity level requires the presence of all the previous parity levels. .PP The same considerations of the \'parity\' option apply. diff --git a/snapraid.txt b/snapraid.txt index 863d8c6e..9621e04d 100644 --- a/snapraid.txt +++ b/snapraid.txt @@ -391,7 +391,7 @@ This command will take a long time, but if you are not paranoid, you can skip it. ---- 4.4.4 STEP 4 -> Sync ---- -Run the "sync" command to resynchronize the array with the new disk. +Run the "sync" command to re-synchronize the array with the new disk. snapraid sync @@ -476,7 +476,7 @@ Spins up all the disks of the array. You can spin-up only some specific disks using the -d, --filter-disk option. -Take care that spinniup-up all the disks at the same time needs a lot of power. +Take care that spinning-up all the disks at the same time needs a lot of power. Ensure that your power-supply can sustain that. Nothing is modified. @@ -643,7 +643,7 @@ Verify all the files and the parity data. It works like "fix", but it only simulates a recovery and no change is written in the array. -This command is mostly intended for manual verifications, +This command is mostly intended for manual verification, like after a recovery process or in other special conditions. For periodic and scheduled checks uses "scrub". @@ -668,7 +668,7 @@ Nothing is modified. Lists all the duplicate files. Two files are assumed equal if their hashes are matching. The file data is not read, but only the -precomputed hashes are used. +pre-computed hashes are used. Nothing is modified. @@ -682,7 +682,7 @@ The files are not really copied here, but just linked using symbolic links. When updating, all the present symbolic links and empty -subdirectories are deleted and replaced with the new +sub-directories are deleted and replaced with the new view of the array. Any other regular file is left in place. Nothing is modified outside the pool directory. @@ -708,20 +708,20 @@ Nothing is modified. 5.14 touch ---------- -Sets arbitrarely the sub-second timestamp of all the files +Sets arbitrarily the sub-second time-stamp of all the files that have it at zero. This improves the SnapRAID capability to recognize moved -and copied files as it makes the timestamp almost unique, +and copied files as it makes the time-stamp almost unique, removing possible duplicates. -More specifically, if the sub-second timestamp is not zero, +More specifically, if the sub-second time-stamp is not zero, a moved or copied file is identified as such if it matches -the name, size and timestamp. If instead the sub-second timestamp +the name, size and time-stamp. If instead the sub-second time-stamp is zero, it's considered a copy only if it matches the full path, -size and timestamp. +size and time-stamp. -Note that the second precision timestamp is not modified, +Note that the second precision time-stamp is not modified, and all the dates and times of your files will be maintained. 5.15 rehash @@ -843,7 +843,7 @@ SnapRAID provides the following options: from the array after the last "sync". If you still have such files, they could be used by "check" and "fix" to improve the recover process. - The files are read also in subdirectories and they are + The files are read also in sub-directories and they are identified regardless of their name. This option can be used only with "check" and "fix". @@ -899,7 +899,7 @@ SnapRAID provides the following options: to another, and to reuse the already computed hash information to detect silent errors or to recover missing files. This behavior, in some rare cases, may result in false positives, - or in a slow process due the many hash verifications, and this + or in a slow process due the many hash verification, and this option allows to resolve them. This option can be used only with "sync", "check" and "fix". @@ -1037,7 +1037,7 @@ is enabled: * 5-parity enables penta (five) parity * 6-parity enables hexa (six) parity -Each parity level requires the precence of all the previous parity +Each parity level requires the presence of all the previous parity levels. The same considerations of the 'parity' option apply.