diff --git a/authors.html b/authors.html index 0efc4059..d3681def 100644 --- a/authors.html +++ b/authors.html @@ -24,7 +24,7 @@
-Title +Title
About @@ -62,17 +62,17 @@ You can contact me by email using the address
Donate with -
-PayPal -BitCoin +
+PayPal +BitCoin
Find other resources at -
-GitHub -SourceForge -TravisCI +
+GitHub +SourceForge +TravisCI
diff --git a/compare.html b/compare.html index 632241c9..54b4ac67 100644 --- a/compare.html +++ b/compare.html @@ -24,7 +24,7 @@
-Title +Title
About @@ -95,17 +95,17 @@ and if all your disks are spinning when reading one file SnapRAIDunRAIDFlexRAIDdisParityZFSBtrfsStorage Spaces -Redundancy model
Real-time computes parity at real-time like RAID, +Redundancy model
Real-time computes parity at real-time like RAID, snapshot at request time, like Backup. -SnapshotReal-timeReal-time
SnapshotSnapshotReal-time
SnapshotReal-time
SnapshotReal-time +SnapshotReal-timeReal-time
SnapshotSnapshotReal-time
SnapshotReal-time
SnapshotReal-time -Integrity
+Integrity
If data is validated with some kind of checksum, -and which one is the default. -Yes
SpookyHash
128 bitNoYes
Adler32
32 bitYes
MD5
128 bitYes
fletcher4
256 bitYes
CRC32C
32 bitNo +and which one is the default. +Yes
SpookyHash
128 bitNoYes
Adler32
32 bitYes
MD5
128 bitYes
fletcher4
256 bitYes
CRC32C
32 bitNo -Fix silent errors
-If silent errors are detected and fixed before they can propagate into the parity. +Fix silent errors
+If silent errors are detected and fixed before they can propagate into the parity. YesNo [1]No [2]NoYes [3]Yes [3]No -Number of failures
+Number of failures
How many disk failures are supported? 1 is for RAID5, 2 for RAID6. 1 2 3 4 5 611 2 3 4 5 6+11 2 31 21 -Other failures
If more disks fail than the supported redundancy model, +Other failures
If more disks fail than the supported redundancy model, is it possible to recover the data in the not failed disks? YesYesYesYesNoNoNo -Power/Noise
How many disks are spinning when reading a single file? +Power/Noise
How many disks are spinning when reading a single file? OneOneOneOneAllAllAll -Filled disks
Can you start with already filled disks? +Filled disks
Can you start with already filled disks? YesPartial[4]YesYesNoNoNo -Add disks
Can you add disks at later time? +Add disks
Can you add disks at later time? YesYesYesYesNoYesYes -Operating system
Which OS is supported? -Linux
Windows
Mac OS X
OpenIndiana
Solaris
BSDLinuxWindows
LinuxWindowsLinux [5]
Mac OS X
OpenIndiana
Solaris
BSDLinuxWindows +Operating system
Which OS is supported? +Linux
Windows
Mac OS X
OpenIndiana
Solaris
BSDLinuxWindows
LinuxWindowsLinux [5]
Mac OS X
OpenIndiana
Solaris
BSDLinuxWindows -Age
The year of the first official release supporting at least RAID5 redundancy. +Age
The year of the first official release supporting at least RAID5 redundancy. 2011200520082009200520132012 -License/Price
+License/Price
Software license and price. -Open Source GPL3
FreeOpen Source GPL2
89$/129$Proprietary
40$/60$Proprietary
FreeOpen Source CDDL
FreeOpen Source GPL2
FreeProprietary
Windows 8 +Open Source GPL3
FreeOpen Source GPL2
89$/129$Proprietary
40$/60$Proprietary
FreeOpen Source CDDL
FreeOpen Source GPL2
FreeProprietary
Windows 8 -Interface
Which interface is provided? GUI or command line? +Interface
Which interface is provided? GUI or command line? -command line
or Elucidate GUI, +command line
or Elucidate GUI, or plugin for for OpenMediaVault -command line
GUIGUIcommand linecommand line
GUI/Plugins [6]command lineGUI +command line
GUIGUIcommand linecommand line
GUI/Plugins [6]command lineGUI @@ -193,7 +193,7 @@ the parity is automatically recomputed, making impossible to recover the silent are not verified when data is read to update the parity. This means that any silent error present will propagate into the parity, making impossible to fix it later, even if it can be still detected comparing the file checksum. -
+
You can get in a state where the "Validate" operation reports errors, but the "Verify" one reports no problem in the parity, making impossible to fix the errors. @@ -203,19 +203,19 @@ making impossible to fix the errors. [3] - ZFS and Btrfs provide a bit-rot protection at the same level of SnapRAID, always checking data before using it. In this regards all the three solutions represent the state-of-the-art. -
+
A cons of ZFS is that the default Fletcher checksum is a choice that favorites speed over quality. The same for the default CRC32C used by Btrfs. The 128 bits SpookyHash used by SnapRAID is instead the state-of-the-art in checksumming quality, without compromising in speed. -
+
Another cons of ZFS is that it lacks a fast RAID implementation in assembler. It only has a C implementation, that is from two to four times slower than SnapRAID/Btrfs. -
+
ZFS also uses a sub-optimal RAID-Z3 algorithm, that requires double computations than the equivalent SnapRAID's z-parity. -
+
Instead, both SnapRAID and Btrfs use top-notch assembler implementations to compute the RAID parity, always using the best known RAID algorithm and implementation.

@@ -245,17 +245,17 @@ If you think that some information reported is incorrect or simply unfair, pleas
Donate with -
-PayPal -BitCoin +
+PayPal +BitCoin
Find other resources at -
-GitHub -SourceForge -TravisCI +
+GitHub +SourceForge +TravisCI
diff --git a/design.html b/design.html index f1c6917e..bb892882 100644 --- a/design.html +++ b/design.html @@ -24,7 +24,7 @@
-Title +Title
About @@ -90,17 +90,17 @@ As internal data base it's used the TommyDS
Donate with -
-PayPal -BitCoin +
+PayPal +BitCoin
Find other resources at -
-GitHub -SourceForge -TravisCI +
+GitHub +SourceForge +TravisCI
diff --git a/download.html b/download.html index 19d97938..c29df240 100644 --- a/download.html +++ b/download.html @@ -24,7 +24,7 @@
-Title +Title
About @@ -93,17 +93,17 @@ Donations are spent on stuffs related to SnapRAID development like to buy new ha
Donate with -
-PayPal -BitCoin +
+PayPal +BitCoin
Find other resources at -
-GitHub -SourceForge -TravisCI +
+GitHub +SourceForge +TravisCI
diff --git a/faq.html b/faq.html index 6ebf56a8..590fd816 100644 --- a/faq.html +++ b/faq.html @@ -24,7 +24,7 @@
-Title +Title
About @@ -70,7 +70,7 @@ Frequently Asked Questions for SnapRAID.
  • Which filesystem is recommended for SnapRAID ?
  • Which hardware configuration is recommended?
  • Is a multi-core CPU recommended?
    • -
  • Is a 64 bit operating system recommended?
    • +
  • Is a 64 bit operating system recommended?
  • How much memory SnapRAID requires to run?
  • Do I have to check the SMART attributes of my disks?
  • Is it possible to use SnapRAID in a dual boot configuration, like Windows and Linux?
    • @@ -162,6 +162,7 @@ For example, with SnapRAID, if you delete by accident a file, you can easily res

    Others advantages over traditional RAID5/6 solutions are: +

    +

    Obviously RAID has other advantages, like having a better speed due data striping. What is best for you, depends on your specific use case.

    @@ -189,6 +191,7 @@ after a complete disk failure.

    SnapRAID is more similar at the RAID-Z/RAID functionality of ZFS/Btrfs. Compared to them, SnapRAID has the following advantages: +

    +

    Obviously ZFS/Btrfs have other advantages, like being real-time solutions. What is best for you, depends on your specific use case.

    @@ -251,13 +255,13 @@ with any other pooling solutions.

    For encryption, SMART monitoring, Power control and Data Recovery you can use other tools. Here some suggestions: -

    +

    LinuxWindowsMac OS X
    Encryption -dmcrypt/LUKS
    +dmcrypt/LUKS
    (tutorial)