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

Minor changes at the manual.

Browse source
This commit is contained in:
Andrea Mazzoleni 2014-11-24 21:50:01 +01:00
parent 01b1f9a2cc
commit be1332f4a1
3 changed files with 15 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

10
snapraid.1
View file

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

10
snapraid.d
View file

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

10
snapraid.txt
View file

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