diff --git a/authors.html b/authors.html index d3681def..60bf6128 100644 --- a/authors.html +++ b/authors.html @@ -23,10 +23,10 @@
-
diff --git a/compare.html b/compare.html
index 54b4ac67..dcd64af7 100644
--- a/compare.html
+++ b/compare.html
@@ -23,10 +23,10 @@
-
diff --git a/design.html b/design.html
index bb892882..880f6bd7 100644
--- a/design.html
+++ b/design.html
@@ -23,10 +23,10 @@
-
diff --git a/download.html b/download.html
index c29df240..d38dcbc7 100644
--- a/download.html
+++ b/download.html
@@ -23,10 +23,10 @@
-
diff --git a/faq.html b/faq.html
index 590fd816..688fa6b6 100644
--- a/faq.html
+++ b/faq.html
@@ -23,10 +23,10 @@
-
SnapRAID is an application able to make a partial backup of your disk array. If some of the disks of your array fail, even if they are completely broken, you will be able to recover their content. @@ -151,7 +155,7 @@ It's only a partial backup, because it doesn't allow to recover from a failure o but only if the number of failed disks are under a predefined limit.
-RAIDs are mirroring solutions that propagate changes immediately to the parity data. In this sense, RAIDs are not backups, because they don't allow to restore an old state of the array. @@ -182,7 +186,7 @@ Obviously RAID has other advantages, like having a better speed due data stripin What is best for you, depends on your specific use case.
-SnapRAID creates a filesystem snapshot conceptually similar at other snapshot solutions. The difference is that the purpose of SnapRAID is to be able to recover a disk to the saved state @@ -208,7 +212,7 @@ Obviously ZFS/Btrfs have other advantages, like being real-time solutions. What is best for you, depends on your specific use case.
-With a normal backup solution you always need as much space as the full disk array for the backup. With SnapRAID you need only one additional parity disk to be able to recover the most common case of a single disk failure. @@ -220,7 +224,7 @@ it's surely the preferred solution if you can afford it. SnapRAID is a good option if a full backup is not a possible solution.
-You can see the Compare page to see it compared to other similar solutions.
@@ -230,24 +234,24 @@ of the ZFS and Btrfs filesystems. Instead, unRAID and Storage Space have no inte FlexRAID is at least able to report silent errors, but not to fix them. -Nothing. It's a FreeSoftware application released with the GPLv3 license.
-Go to the Forum.
-No. SnapRAID is a command line application. But there is the Elucidate external GUI, and a plugin for OpenMediaVault.
-
SnapRAID provides a basic virtual views/storage pooling solution, but it's also compatible
with any other pooling solutions.
@@ -332,7 +336,7 @@ Dead site?
-Is SnapRAID suitable to backup the home/My Documents directory?
+
No. If you have a limited amount of data that can be easily saved in an external USB HD, or in online backup services, it doesn't make sense to use SnapRAID. @@ -341,7 +345,7 @@ many Tera bytes, and a full backup copy of a such amount of data is not possible in any other way.
-
No. For the disk used for booting your machine and containing the OS files,
it's better to use another solution, like RAID1 or a mirror copy.
@@ -352,7 +356,7 @@ SnapRAID needs an OS to run, and then it cannot recover the OS if the OS is miss
For a setup example in Ubuntu 14.04 you can check the SnapRAID Zack's tutorial.
-Do I need one or more parity disks?
+
As a rule of thumb you can stay with one parity disk (RAID5) with up to four data disks, and then using one parity disk for each group of seven data disks, like in the table: @@ -406,7 +410,7 @@ Some interesting articles about number of parity levels and failure rate of disk How long do disk drives last?.
-For the data disks, you can use whatever filesystem you like. For the parity disks, follow these suggestions: @@ -460,7 +464,7 @@ Like:
mkfs.ext4 -m 0 -T largefile4 DEVICE-
For best performance it's recommended to have all the disks connected with SATA and not with USB.
@@ -473,7 +477,7 @@ For choosing harddisk, you can check Backblaze's Enterprise Drives: Fact or Fiction?. -No. SnapRAID is usually not CPU bound. The limiting factor is the read performance from disks. So, also a single core CPU should be enough. @@ -483,7 +487,7 @@ For example, in my system I get a combined read speed of 400 MiB/s, but SnapRAID is able to hash at 12000 MiB/s in a single core.
-Yes. SnapRAID works better in a 64 bit operating system. It can access more than 4 GiB of memory, and use faster hashing and parity algorithms. @@ -491,7 +495,7 @@ Anyway, if you have less than 30 TB of data, it performs very well also using a operating system.
-Approximatively, the 32 bits version of SnapRAID requires 1 GiB of memory for 9 TB of data. The 64 bits version requires 1 GiB of memory for 7 TB of data. @@ -510,7 +514,7 @@ in the parity files. Note that running with memory swapped to disk is not recommended because it will be a huge slowdown.
-Yes! 20% of the disks die before 4 years of life, as reported by Backblaze's How long do disk drives last?. @@ -546,7 +550,7 @@ that also recommens to replace the disk after the first error in the SMART attri Current_Pending_Sector (197) and Offline_Uncorrectable (198).
-Yes. It's possible to use SnapRAID in a dual boot configuration. Doesn't matter the OS combination used.
@@ -559,7 +563,7 @@ like using different SnapRAID version, configuration, content files, and so on.It's the file used by SnapRAID to save the list of all files present in your array with all the checksum, timestamp and any other information needed. @@ -569,7 +573,7 @@ These file will be of about few GiB depending of how big is your array. Approximatively for 10 TB of data, you'll need 500 MiB of content file.
-They are the files used by SnapRAID to store the parity data used in recovering.
@@ -578,7 +582,7 @@ These files will grow in size as the biggest amount of data stored in a single d of the array. -
To configure SAMBA to share the pool directory, for example /pool, you should add to
your /etc/samba/smb.conf the following options:
@@ -596,7 +600,7 @@ guest ok = yes
wide links = yes
-How to use more disks than drive letters in Windows?
+
You can use Volume Mount points. You can mount a disk in a directory without using a drive letter. Just like in Linux. @@ -604,7 +608,7 @@ using a drive letter. Just like in Linux.
If you want to minimize the probability to lose data, do this:
@@ -620,7 +624,7 @@ At the first Reallocated_Sector_Ct, Current_Pending_Sector or O even if it still works. -
To add a new data disk at the array, add the new "disk" option in the configuration file,
and then run a "sync" command.
@@ -629,7 +633,7 @@ and then run a "sync" command.
snapraid sync
-How can I remove a data disk from an existing array?
+
To remove a data disk from the array do:
@@ -647,7 +651,7 @@ The "-E" option tells at SnapRAID to proceed even when detecting an empty disk.< Your array is now without any reference to the removed disk. -To add a new parity level, add the proper "N-parity" option in the configuration file, and then run the "sync" command, using the "F, --force-full" option: @@ -670,7 +674,7 @@ Take care that after removing a parity file, you cannot reuse it anymore, because it gets outdated after the next "sync" command.
-
If you lost the disk, see the recovering section in the manual.
Otherwise, copy all the files in the new disk,
@@ -702,7 +706,7 @@ Finally you can run "sync" to update the SnapRAID state. This command will be al
snapraid sync
-How can I replace a parity disk?
+
If the disk is still accessible, first ensure to have a synched array running a sync command:
@@ -738,12 +742,12 @@ If instead you completely lost the parity file, you can run the "fix" command to snapraid fix -Yes, you can defragment data and parity disks. Defragmentation doesn't invalidate the SnapRAID data.
-To upgrade SnapRAID to a new version, just replace the old SnapRAID executable with the new one. The new SnapRAID will use your existing configuration, content and parity files. @@ -759,7 +763,7 @@ You can anyway try, and if the old SnapRAID is not able to read the new content you will be advised by a proper message.
-TrueCrypt by default has enabled the option Preserve modification timestamp of file containers that makes impossible to SnapRAID, and other backup programs, to detect that a file container is changed. @@ -768,7 +772,7 @@ Ensure to disable this option in TrueCrypt.
Simply run the "fix" command using a filter for the specified file. Like:
@@ -788,13 +792,13 @@ To undelete all the missing files use: snapraid fix -m -All the files added in the broken disk after the last "sync" command are lost. All the other data is safe and it can be recovered.
-
In the worst case, any file deleted or modified in not broken disks may prevent to recover the same amount of data in the broken disk.
For example, if you deleted 10GB of data, you may not be able to recover 10GB of data from the broken disk.
@@ -814,7 +818,7 @@ the deleted files are stored:
snapraid fix -i dir_of_deleted_files
-What happen if a disk breaks during a "sync" ?
+
You are still able to recover data. In the worst case, you will be able to recover as much data as if the disk would have broken before the "sync". @@ -824,7 +828,7 @@ To improve the recovering you can also use the "autosave" configuration option t content file during the sync process.
-Syncing... 309505: Data error for file d4/data/index.db at position 40960 @@ -877,7 +881,7 @@ to set the timestamp. To avoid all these Windows problems, simply ensure to run "sync" when no program is using the files into the array. --How can I store in a file all the messages from a check and fix command
+How can I store in a file all the messages from a check and fix command
To generate a log file you can use the "-l" option.
@@ -885,7 +889,7 @@ To generate a log file you can use the "-l" option. snapraid check -l mylog.log
There is the dedicated -C, --gen-conf command that writes a template configuration file compatible with your content file. @@ -898,15 +902,15 @@ snapraid -C snapraid.content > snapraid.conf.new
No. SnapRAID is a single thread application. Considering that SnapRAID is usually not CPU bound, there is no need to have a multithread application. @@ -933,7 +937,7 @@ Take care that that being singlethread doesn't mean that SnapRAID has to wait wh The read-ahead functionality of modern operating systems, ensures that SnapRAID never has to wait for data.
-Before the sync process start, SnapRAID saves a special content file that contains a description of both the states before and after the sync. @@ -949,7 +953,7 @@ ignoring any new file added in the array. Also in this case, using a double parity helps to recover when there are overlapping changes in the array.
-Yes. You can safely read from data disks while a 'sync' is running.
@@ -962,7 +966,7 @@ This obviously could affect a potential recovery, but it's just like if you wrot just after the 'sync' completed. -No. SnapRAID never retries disk operations. At the first reported Input/Output error, it just stops the execution. @@ -984,7 +988,7 @@ In the case of "sync" command, the latest state is anyway saved before terminati So, just restarting it will continue where stopped.
-It's a file used by SnapRAID to check if another SnapRAID instance is already running. It's created where the first content file is placed. @@ -992,7 +996,7 @@ It's created where the first content file is placed.
The most important factor is to connect all the disks using (E)SATA connections, to avoid slowdown caused by the controller. Avoid any kind of USB disks. @@ -1008,7 +1012,7 @@ As last, a fast CPU could improve the speed when having a lot of disks. You can detect if the CPU is a limiting factor, checking the CPU usage during sync operations.
-The default blocksize should be already the best one.
@@ -1017,7 +1021,7 @@ Note that increasing it doesn't necessarely improve the performance. In some cases, it could decrease it. -The default Linux read-ahead size of 128 KiB already ensures the best performance for the default SnapRAID block size of 256 KiB. @@ -1036,7 +1040,7 @@ Note that if you want to use a SnapRAID block size smaller than 256 KiB, it's re read-ahead size, and just use the default value.
-Murmur3 hash is very fast on 32 bits, SpookyHash is even faster on 64 bits. The speed of parity computation is always good up to double parity, @@ -1096,7 +1100,7 @@ RAID functions used for recovering with 'fix':
Likely you have too few free memory, and the Linux out-of-memory OOM killer terminates SnapRAID because it's using too much memory. @@ -1109,7 +1113,7 @@ free -m If it's too small, you have to install more memory in the machine.
-This means that SnapRAID needs to grow the parity file to a size that cannot be contained in the parity disk. @@ -1134,16 +1138,16 @@ The '-T largefile4' and '-m 0' options should give more space available for the
diff --git a/index.html b/index.html
index ff658109..0a75a546 100644
--- a/index.html
+++ b/index.html
@@ -23,10 +23,10 @@
-
diff --git a/manual.html b/manual.html
index 2c1347fe..1aae1f6b 100644
--- a/manual.html
+++ b/manual.html
@@ -23,10 +23,10 @@
-
diff --git a/style.css b/style.css
index 37e0f4b5..95dc9efb 100644
--- a/style.css
+++ b/style.css
@@ -86,43 +86,43 @@ body {
overflow-y:scroll;
}
-/* title */
+/* header */
-#title {
+#header {
background:#0a64a4;
padding:0px;
}
-#title img {
+#header img {
width:100%;
/* avoid to scale up the image */
max-width:1200px;
height:auto;
}
-/* bar */
+/* menu */
-#bar {
+#menu {
background-color:#bacad9;
padding:8px;
padding-left:5%;
padding-right:5%;
}
-#bar a {
+#menu a {
color:#0c5da5;
font-family:sans-serif;
padding-left:1em;
font-weight:bold;
}
-#bar .bold {
+#menu .bold {
color:#0c5da5;
}
-/* bottombar */
+/* footer */
-#bottombar {
+#footer {
background-color:#bacad9;
min-height:90px;
padding-top:16px;
@@ -132,22 +132,22 @@ body {
overflow:auto;
}
-#bottombar a {
+#footer a {
color:#0c5da5;
font-family:sans-serif;
padding-left:1em;
}
-#bottombar .bold {
+#footer .bold {
color:#0c5da5;
}
-.half {
+.column {
float:left;
width:50%;
}
-.half img {
+.column img {
/* scale down the image if there is no space */
max-width:50%;
height:auto;