From 44b11d5d99032af75e4a98732659f65f0555935d Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Wed, 9 Sep 2015 23:33:37 +0200 Subject: [PATCH] Auto update --- compare.html | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/compare.html b/compare.html index b66661f0..632241c9 100644 --- a/compare.html +++ b/compare.html @@ -46,6 +46,8 @@

The best known others are: +

+ -

The main factor to categorize them is when the redundancy information is updated. @@ -105,7 +106,7 @@ and which one is the default. 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 +YesNo [1]No [2]NoYes [3]Yes [3]No Operating system
Which OS is supported? -Linux
Windows
Mac OS X
OpenIndiana
Solaris
BSDLinuxWindows
LinuxWindowsLinux [5]
Mac OS X
OpenIndiana
Solaris
BSDLinuxWindows +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. 2011200520082009200520132012 @@ -175,20 +176,20 @@ Software license and price. 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

Notes

-[1] - unRAID doesn't have any kind of checksum, and it just ignores silent errors. +[1] - unRAID doesn't have any kind of checksum, and it just ignores silent errors. Even worse, if a parity error is detected as result of a silent error in the data, the parity is automatically recomputed, making impossible to recover the silent error, even manually.

-[2] - Flexraid uses checksums to validate files, but such checksums +[2] - Flexraid uses checksums to validate files, but such checksums 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. @@ -199,7 +200,7 @@ making impossible to fix the errors.

-[3] - ZFS and Btrfs provide a bit-rot protection at the same level of SnapRAID, +[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.
@@ -220,16 +221,16 @@ always using the best known RAID algorithm and implementation.

-[4] - unRAID allows to use filled disks but only if they are already +[4] - unRAID allows to use filled disks but only if they are already formatted with the ReiserFS, XFS or Btrfs filesystems. But not ext4 or NTFS.

-[5] - ZFS is also available in Linux at kernel level using ZFS on Linux. +[5] - ZFS is also available in Linux at kernel level using ZFS on Linux.

-[6] - ZFS has external GUIs, like Napp-it +[6] - ZFS has external GUIs, like Napp-it and plugins for FreeNAS and NAS4Free.