diff --git a/HISTORY b/HISTORY index 4007f02e..140c2ffa 100644 --- a/HISTORY +++ b/HISTORY @@ -33,7 +33,7 @@ SnapRAID HISTORY * Increased by one the minimum number of content files. Before it was only a suggestion, but now it's a requirement because you are allowed to put content files in data disks. -* Added checks to ensure that data and parity disks are diffent, and to +* Added checks to ensure that data and parity disks are different, and to correctly count the number of copies of "content" files in different disks. * Removed the dependency of the "disk" order specification in the configuration file. The used order is now saved in the content file to avoid to damage the @@ -54,7 +54,7 @@ SnapRAID HISTORY 1.6 2011/9 ========== * The content file is now saved also at the start of the "sync" command. - This avoids parity errors if the sync process aborted without + 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 @@ -89,7 +89,7 @@ SnapRAID HISTORY to remove the warning. * In fixing, if a file cannot be written for missing permission, an error is reported only if a write is effectively required. -* Ignores any symbolic links. They are not backuped. +* Ignores any symbolic links. They are not saved. 1.3 2011/5 ========== diff --git a/TODO b/TODO index f0a5c00c..2f3aaf4f 100644 --- a/TODO +++ b/TODO @@ -22,6 +22,9 @@ on the error message. See: https://sourceforge.net/projects/snapraid/forums/foru * Support interrupted operations with EINTR. For remote filesystems it could be relevant. +* In Windows we must be case insensitive, at least for ASCII<128 comparison. For other UTF-8 chars +is too complex. + - v2.x * Remove the old MD5 support. diff --git a/snapraid.1 b/snapraid.1 index 299b7a9f..7a1bf64e 100644 --- a/snapraid.1 +++ b/snapraid.1 @@ -272,7 +272,16 @@ system. For example, you can use it to recover from an accidentally deleted directory, simply running the fix command like. .PP .RS 4 -snapraid fix \(hyf JUST_DELETED_DIR/ +snapraid fix \(hyf DIR/ +.PD 0 +.PP +.PD +.RE +.PP +Or to simply recover one file you can use: +.PP +.RS 4 +snapraid fix \(hyf FILE .PD 0 .PP .PD diff --git a/snapraid.d b/snapraid.d index 2d55d380..37f2988f 100644 --- a/snapraid.d +++ b/snapraid.d @@ -159,7 +159,11 @@ Getting Started system. For example, you can use it to recover from an accidentally deleted directory, simply running the fix command like. - :snapraid fix -f JUST_DELETED_DIR/ + :snapraid fix -f DIR/ + + Or to simply recover one file you can use: + + :snapraid fix -f FILE Commands SnapRAID provides four simple commands that allow to: diff --git a/snapraid.txt b/snapraid.txt index d90c75d7..91831202 100644 --- a/snapraid.txt +++ b/snapraid.txt @@ -172,7 +172,11 @@ In this regard snapraid is more like a backup program than a RAID system. For example, you can use it to recover from an accidentally deleted directory, simply running the fix command like. - snapraid fix -f JUST_DELETED_DIR/ + snapraid fix -f DIR/ + +Or to simply recover one file you can use: + + snapraid fix -f FILE 5 COMMANDS