Some final changes.

This commit is contained in:
Andrea Mazzoleni 2011-11-16 20:42:27 +01:00
parent 550a2266cf
commit a2344cf159
4 changed files with 49 additions and 49 deletions

View file

@ -208,7 +208,7 @@ Commands
command to update the new state of the files.
All the files that cannot be fixed are renamed adding
the '.unrecoverable' extension.
the ".unrecoverable" extension.
The "content" file is NOT modified.
The "parity" and "q-parity" files are modified if necessary.
@ -219,7 +219,7 @@ Options
-c, --conf CONFIG
Selects the configuration file. If not specified it's assumed
the file '/etc/snapraid.conf' in Unix, and 'snapraid.conf' in
the file "/etc/snapraid.conf" in Unix, and "snapraid.conf" in
the current directory in Windows.
-f, --filter PATTERN
@ -233,13 +233,13 @@ Options
-N, --find-by-name
When syncing finds the files by name instead than by inode.
This option allows a fast sync command after having replaced
one physical disk with another copying manually the files.
Without this option the 'sync' command recognizes that
one physical disk with another, copying manually the files.
Without this option the "sync" command recognizes that
the files were copied to a different disk, and it will resync
them all. Instead, with this option, a file with the correct
name, size and time is assumed identical at the previous
one.
This option has effect only on the 'sync' and 'diff' commands.
This option has effect only on the "sync" and "diff" commands.
-Z, --force-zero
Forces the insecure operation of syncing a file with zero
@ -488,7 +488,7 @@ Recovering
DO NOT PANIC! You will be able to recover it!
The first thing you have to do is to avoid futher changes at you disk array.
Disable any remote connections to it, any scheduled processes, including any
Disable any remote connection to it, any scheduled process, including any
scheduled SnapRAID nightly sync.
Then proceed with the following steps.
@ -497,7 +497,7 @@ Recovering
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.
Change the SnapRAID configuration and change the 'disk' directory
Change the SnapRAID configuration and change the "disk" directory
of the failed disk to point to the new empty space.
STEP 2 -> Fix
@ -517,15 +517,15 @@ Recovering
checking all the lines starting with "unrecoverable:"
If you are not satified of the recovering, you can retry it as many time you wish.
For example, if you have moved away some files from other disks after the last 'sync',
you can retry to put them inplace, and retry the 'fix'.
For example, if you have moved away some files from other disks 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 synching you will no more able to retry the
'fix' command!
"fix" command!
STEP 3 -> Check
As paranoid check, you can now run a whole 'check' command to ensure that
As paranoid check, you can now run a whole "check" command to ensure that
everything is OK.
:snapraid check
@ -533,11 +533,11 @@ Recovering
This command will take a long time.
STEP 4 -> Sync
Run the 'sync' command to resyncronize the array with the new disk.
Run the "sync" command to resyncronize the array with the new disk.
To avoid a long time sync you can use the '--find-by-name' option to
To avoid a long time sync you can use the "--find-by-name" option to
force SnapRAID to ignore the fact that all the recovered files are now in
a different physical disk, and they don't need to be synched.
a different physical disk, but they are not changed.
:snapraid --find-by-name sync