Minor changes at the documentation

This commit is contained in:
Andrea Mazzoleni 2015-04-21 21:13:59 +02:00
parent de0c437bd2
commit 618af56a13
4 changed files with 17 additions and 17 deletions

10
HISTORY
View file

@ -13,7 +13,7 @@ SnapRAID HISTORY
* The -e, --filter-error option doesn't write anymore fixes to
unsynced files. This helps in case you are running it on a not
synced array, removing the risk to revert some files to an old state.
* The -e, --filter-error option is now optimal and read only the
* The -e, --filter-error option is now optimal and reads only the
minimal amount of data necessary to fix the errors.
* The "diff" command returns with an error code if a "sync" is
required.
@ -55,7 +55,7 @@ SnapRAID HISTORY
timestamp, and then they are recognized also if moved to a different
disk. Note that even if there are false positive they are identified
checking the hash, so they have not effect, besides making the
process a little slower. To disable this new behaviour you can use
process a little slower. To disable this new behavior you can use
the -N, --force-nocopy option.
* The -i, --import command now identifies files by timestamp making it
very fast in importing directories.
@ -221,7 +221,7 @@ SnapRAID HISTORY
4.1 2013/9
==========
* If the underline filesystem doesn't support the FIEMAP command,
automatically fallback to use FIBMAP for sorting files.
automatically fall back to use FIBMAP for sorting files.
* Fixed the import of content files from previous version of SnapRAID that
are the result of an incomplete sync.
* Added a new -C, --gen-conf option to generate a dummy configuration
@ -389,7 +389,7 @@ SnapRAID HISTORY
disks instead than in the parity disks.
* Added a checksum at the content file to ensure its integrity.
* Using fallocate() instead posix_fallocate() to avoid the very slow
posix_fallocate() fallback of writing the whole file.
posix_fallocate() fall back of writing the whole file.
1.7 2011/11
===========
@ -425,7 +425,7 @@ SnapRAID HISTORY
This avoids parity errors if the sync process is aborted without
saving the content file and you made changes at the disk array before
another "sync" command was done.
More specifically, deletions or truncations of not yet synched files
More specifically, deletions or truncations of not yet synced files
after the aborted sync, and before the next sync command, may have damaged
the parity data. New file additions were instead safe.
If these conditions may have happened to you a "check" command (also

View file

@ -596,7 +596,7 @@ time you wish.
For example, if you have removed files from the array after the last
\[dq]sync\[dq], this may result in some other files not recovered.
In this case, you can retry the \[dq]fix\[dq] using the \-i, \-\-import option,
specifing where these files are now, to include them again in the
specifying where these files are now, to include them again in the
recovering process.
.PP
If you are satisfied of the recovering, you can now proceed further,
@ -793,7 +793,7 @@ state saved in the last \[dq]sync\[dq].
If a difference is found, it\'s reverted to the stored snapshot.
.PP
Note that \[dq]fix\[dq] doesn\'t differentiate between errors and intentional
modifications. It inconditionally reverts the file state at the last \[dq]sync\[dq].
modifications. It unconditionally reverts the file state at the last \[dq]sync\[dq].
.PP
If no other option is specified the full array is processed.
Use the filter options to select a subset of files or disks to operate on.
@ -870,7 +870,7 @@ The next two columns are the high level device id and path.
The latest column if the disk name in the array.
.PP
In most cases you have one low level device for each disk in the
array, but in some more complex configurations, you may have multple
array, but in some more complex configurations, you may have multiple
low level devices used by a single disk in the array.
.PP
Nothing is modified.
@ -1068,7 +1068,7 @@ you can use respectively \[dq]>&1\[dq] and \[dq]>&2\[dq].
.TP
.B \-L, \-\-error\-limit
Sets a new error limit before stopping execution.
By default SnapRAID stops if it encouters more than 100
By default SnapRAID stops if it encounters more than 100
Input/Output errors, meaning that likely a disk is going to
die.
This options affects \[dq]sync\[dq] and \[dq]scrub\[dq], that are allowed

View file

@ -331,7 +331,7 @@ Getting Started
For example, if you have removed files from the array after the last
"sync", this may result in some other files not recovered.
In this case, you can retry the "fix" using the -i, --import option,
specifing where these files are now, to include them again in the
specifying where these files are now, to include them again in the
recovering process.
If you are satisfied of the recovering, you can now proceed further,
@ -508,7 +508,7 @@ Commands
If a difference is found, it's reverted to the stored snapshot.
Note that "fix" doesn't differentiate between errors and intentional
modifications. It inconditionally reverts the file state at the last "sync".
modifications. It unconditionally reverts the file state at the last "sync".
If no other option is specified the full array is processed.
Use the filter options to select a subset of files or disks to operate on.
@ -592,7 +592,7 @@ Commands
The latest column if the disk name in the array.
In most cases you have one low level device for each disk in the
array, but in some more complex configurations, you may have multple
array, but in some more complex configurations, you may have multiple
low level devices used by a single disk in the array.
Nothing is modified.
@ -792,7 +792,7 @@ Options
-L, --error-limit
Sets a new error limit before stopping execution.
By default SnapRAID stops if it encouters more than 100
By default SnapRAID stops if it encounters more than 100
Input/Output errors, meaning that likely a disk is going to
die.
This options affects "sync" and "scrub", that are allowed

View file

@ -352,7 +352,7 @@ time you wish.
For example, if you have removed files from the array after the last
"sync", this may result in some other files not recovered.
In this case, you can retry the "fix" using the -i, --import option,
specifing where these files are now, to include them again in the
specifying where these files are now, to include them again in the
recovering process.
If you are satisfied of the recovering, you can now proceed further,
@ -548,7 +548,7 @@ state saved in the last "sync".
If a difference is found, it's reverted to the stored snapshot.
Note that "fix" doesn't differentiate between errors and intentional
modifications. It inconditionally reverts the file state at the last "sync".
modifications. It unconditionally reverts the file state at the last "sync".
If no other option is specified the full array is processed.
Use the filter options to select a subset of files or disks to operate on.
@ -646,7 +646,7 @@ The next two columns are the high level device id and path.
The latest column if the disk name in the array.
In most cases you have one low level device for each disk in the
array, but in some more complex configurations, you may have multple
array, but in some more complex configurations, you may have multiple
low level devices used by a single disk in the array.
Nothing is modified.
@ -851,7 +851,7 @@ SnapRAID provides the following options:
-L, --error-limit
Sets a new error limit before stopping execution.
By default SnapRAID stops if it encouters more than 100
By default SnapRAID stops if it encounters more than 100
Input/Output errors, meaning that likely a disk is going to
die.
This options affects "sync" and "scrub", that are allowed