@@ -158,7 +158,7 @@ With a Backup you are able to recover from a complete failure of the whole disk array.
@@ -230,9 +230,9 @@ parity E:\snapraid.parity content C:\snapraid\snapraid.content content F:\array\snapraid.content content G:\array\snapraid.content -disk d1 F:\array\ -disk d2 G:\array\ -disk d3 H:\array\ +data d1 F:\array\ +data d2 G:\array\ +data d3 H:\array\
@@ -386,7 +386,7 @@ requires the network clients to resolve them remotely.
To make it working, besides sharing in the network the pool directory, you must also share all the disks independently, using as share points -the disk names as defined in the config file. You must also specify in +the disk names as defined in the configuration file. You must also specify in the "share" option of the configure file, the Windows UNC path that remote clients needs to use to access such shared disks.
@@ -395,9 +395,9 @@ the options:
-disk d1 F:\array\ -disk d2 G:\array\ -disk d3 H:\array\ +data d1 F:\array\ +data d2 G:\array\ +data d3 H:\array\ pool C:\pool share \\darkstar@@ -488,7 +488,7 @@ For example, if you have that disk "d1" failed, you can change from:
@@ -496,7 +496,7 @@ to:
4.4.2 @@ -658,7 +658,7 @@ or less parity. This command uses the "smartctl" tool, and it's equivalent to run "smartctl -a" on all the devices.-If your devices are not autodetected correctly, you can configure +If your devices are not auto-detected correctly, you can configure a custom command using the "smartctl" option in the configuration file. @@ -668,6 +668,8 @@ up Spins up all the disks of the array. +You can spin-up only some specific disks using the -d, --filter-disk option. + Nothing is modified. 5.4 down @@ -677,6 +679,8 @@ Spins down all the disks of the array. This command uses the "smartctl" tool, and it's equivalent to run "smartctl -s standby,now" on all the devices.+You can spin-down only some specific disks using the -d, --filter-disk option. + Nothing is modified. 5.5 diff @@ -684,9 +688,58 @@ diff Lists all the files modified from the last "sync" that need to have their parity data recomputed.-This command doesn't check the file data, but only the file timestamp +This command doesn't check the file data, but only the file time-stamp size and inode. +At the end of the command, you'll get a summary of the file changes +grouped by: +
If a "sync" is required, the process return code is 2, instead of the default 0. The return code 1 is instead for a generic error condition. @@ -707,8 +760,8 @@ If during the process, silent or input/output errors are found, the corresponding blocks are marked as bad. Files are identified by path and/or inode and checked by -size and timestamp. -If the file size or timestamp are different, the parity data +size and time-stamp. +If the file size or time-stamp are different, the parity data is recomputed for the whole file. If the file is moved or renamed in the same disk, keeping the same inode, the parity is not recomputed. @@ -787,7 +840,7 @@ All the files that cannot be fixed are renamed adding the Before fixing, the full array is scanned to find any moved file, after the last "sync" operation. -These files are identified by their timestamp, ignoring their name +These files are identified by their time-stamp, ignoring their name and directory, and are used in the recovering process if necessary. If you moved some of them outside the array, you can use the -i, --import option to specify additional directories to scan. @@ -875,6 +928,24 @@ low level devices used by a single disk in the array. Nothing is modified. 5.16 +touch ++Sets arbitrarely the sub-second timestamp of all the files +that have it at zero. ++This improves the SnapRAID capability to recognize moved +and copied files as it makes the timestamp almost unique, +removing possible duplicates. + +More specifically, if the sub-second timestamp is not zero, +a moved or copied file is identified as such if it matches +the name, size and timestamp. If instead the sub-second timestamp +is zero, it's cosidered a copy only if it matches the full path, +size and timestamp. + +Note that the second precision timestamp is not modified, +and all the dates and times of your files will be maintained. + 5.17 rehashSchedules a rehash of the whole array. @@ -926,18 +997,15 @@ process the whole array. | ||||||||||||||||||||||||||
| -d, --filter-disk NAME | ||||||||||||||||||||||||||
| -Filters the files to process in "check" and "fix". -Only the files present in the specified disk are processed. +Filters the disks to process in "check", "fix", "up" and "down". You must specify a disk name as named in the configuration file. -In "check", you can make it faster, specifying also -a, --audit-only -option, to avoid to access other disks to check parity data. -If you combine more --filter, --filter-disk and --filter-missing options, -only files matching all the set of filters are selected. You can also specify parity disks with the names: "parity", "2-parity", "3-parity", ... to limit the operations a specific parity disk. +If you combine more --filter, --filter-disk and --filter-missing options, +only files matching all the set of filters are selected. This option can be used many times. -This option can be used only with "check" and "fix". +This option can be used only with "check", "fix", "up" and "down". Note that it cannot be used with "sync" and "scrub", because they always process the whole array. |
It can be placed in the disk used to store data, parity, or @@ -1316,16 +1384,22 @@ more copies of the same files. You have to store at least one copy for each parity disk used plus one. Using some more doesn't hurt.
You can change the mount point as you like, as long you keep the NAME fixed.
-You should use one option for each disk of the array. +You should use one option for each data disk of the array. +
+You can rename later a disk, changing the NAME directly +in the configuration file, and then run a 'sync' command. +In the rename case, the association is done using the stored +UUID of the disks.
DISK is the same disk name specified in the "disk" option. PARITY is one of the parity name as "parity,[1,2,3,4,5,6,z]-parity". @@ -1472,9 +1546,9 @@ An example of a typical configuration for Unix is: parity /mnt/diskp/snapraid.parity content /mnt/diskp/snapraid.content content /var/snapraid/snapraid.content -disk d1 /mnt/disk1/ -disk d2 /mnt/disk2/ -disk d3 /mnt/disk3/ +data d1 /mnt/disk1/ +data d2 /mnt/disk2/ +data d3 /mnt/disk3/ exclude /lost+found/ exclude /tmp/ smartctl d1 -d sat %s @@ -1491,9 +1565,9 @@ An example of a typical configuration for Windows is: parity E:\snapraid.parity content E:\snapraid.content content C:\snapraid\snapraid.content -disk d1 G:\array\ -disk d2 H:\array\ -disk d3 I:\array\ +data d1 G:\array\ +data d2 H:\array\ +data d3 I:\array\ exclude Thumbs.db exclude \$RECYCLE.BIN exclude \System Volume Information @@ -1515,7 +1589,7 @@ There are four different types of patterns: FILE
Note that when you specify an absolute path starting with /, it's -applied at the array root dir and not at the local filesystem root dir. +applied at the array root dir and not at the local file-system root dir.
In Windows you can use the backslash \ instead of the forward slash /. Note that Windows system directories, junctions, mount points, and any other Windows special directory are treated just as files, meaning that to exclude them you must use a file rule, and not a directory one.
+If the file name you want to use really contains a '*', '?', '[', +or ']' char, you have to escape it to avoid to have interpreted as a +globbing character. In Unix the escape char is '\' in Windows it's '^'. +Note that when the pattern is on the command line, you have to double the +escape character to avoid to have it interpreted by the command shell. +
In the configuration file, you can use different strategies to filter the files to process. The simplest one is to use only "exclude" rules to remove all the @@ -1620,10 +1700,10 @@ quote them. Otherwise the shell will try to expand them.
It's a binary file, listing all the files present in your disk array, -with all the checksums to verify their integrity. +with all the check-sums to verify their integrity.
This file is read and written by the "sync" and "scrub" commands, and read by "fix", "check" and "status". @@ -1642,9 +1722,9 @@ only read by "scrub" and "check". Encoding SnapRAID in Unix ignores any encoding. It reads and stores the -file names with the same encoding used by the filesystem. +file names with the same encoding used by the file-system.
-In Windows all the names read from the filesystem are converted and +In Windows all the names read from the file-system are converted and processed in the UTF-8 format.
To have the file names printed correctly you have to set the Windows