From be1332f4a1e72615c5c676e3db516612be989b5c Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Mon, 24 Nov 2014 21:50:01 +0100 Subject: [PATCH] Minor changes at the manual. --- snapraid.1 | 10 +++++----- snapraid.d | 10 +++++----- snapraid.txt | 10 +++++----- 3 files changed, 15 insertions(+), 15 deletions(-) diff --git a/snapraid.1 b/snapraid.1 index e49ece3c..2748aeca 100644 --- a/snapraid.1 +++ b/snapraid.1 @@ -1323,11 +1323,11 @@ scheduled SnapRAID nightly sync. Then proceed with the following steps. .SS STEP 1 \-> Reconfigure You need some space to recover, even better if you already have an additional -disk, but in case, also an external USB or remote one is enough. +disk, but in case, also an external USB or remote disk is enough. .PP Change the SnapRAID configuration file and make the \[dq]disk\[dq] option -of the failed disk to point to a place where you have enough empty space -to recover the files. +of the failed disk to point to the place where you have enough empty +space to recover the files. .PP For example, if you have that disk \[dq]d1\[dq] failed, you can change: .PP @@ -1374,11 +1374,11 @@ For example, if you have remove some files after the last \[dq]sync\[dq], you ca to put them inplace, and retry the \[dq]fix\[dq]. .PP If you are satisfied of the recovering, you can now proceed further, -but take care that after syncing you will no more able to retry the +but take care that after syncing you will be no more able to retry the \[dq]fix\[dq] command! .SS STEP 3 \-> Check As paranoid check, you can now run a \[dq]check\[dq] command to ensure that everything -is OK on the disk. +is OK on the recovered disk. .PP .RS 4 snapraid \-d NAME \-a check diff --git a/snapraid.d b/snapraid.d index 42ac11de..a46df67b 100644 --- a/snapraid.d +++ b/snapraid.d @@ -962,11 +962,11 @@ Recovering STEP 1 -> Reconfigure You need some space to recover, even better if you already have an additional - disk, but in case, also an external USB or remote one is enough. + disk, but in case, also an external USB or remote disk is enough. Change the SnapRAID configuration file and make the "disk" option - of the failed disk to point to a place where you have enough empty space - to recover the files. + of the failed disk to point to the place where you have enough empty + space to recover the files. For example, if you have that disk "d1" failed, you can change: @@ -999,12 +999,12 @@ Recovering to put them inplace, and retry the "fix". If you are satisfied of the recovering, you can now proceed further, - but take care that after syncing you will no more able to retry the + but take care that after syncing you will be no more able to retry the "fix" command! STEP 3 -> Check As paranoid check, you can now run a "check" command to ensure that everything - is OK on the disk. + is OK on the recovered disk. :snapraid -d NAME -a check diff --git a/snapraid.txt b/snapraid.txt index eec62f9f..930d1057 100644 --- a/snapraid.txt +++ b/snapraid.txt @@ -1036,11 +1036,11 @@ Then proceed with the following steps. ------------------------- You need some space to recover, even better if you already have an additional -disk, but in case, also an external USB or remote one is enough. +disk, but in case, also an external USB or remote disk is enough. Change the SnapRAID configuration file and make the "disk" option -of the failed disk to point to a place where you have enough empty space -to recover the files. +of the failed disk to point to the place where you have enough empty +space to recover the files. For example, if you have that disk "d1" failed, you can change: @@ -1075,14 +1075,14 @@ For example, if you have remove some files after the last "sync", you can retry to put them inplace, and retry the "fix". If you are satisfied of the recovering, you can now proceed further, -but take care that after syncing you will no more able to retry the +but take care that after syncing you will be no more able to retry the "fix" command! 9.3 STEP 3 -> Check ------------------- As paranoid check, you can now run a "check" command to ensure that everything -is OK on the disk. +is OK on the recovered disk. snapraid -d NAME -a check