From e69776f3beed9d97dbd01fe5a4284624349e3155 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Tue, 14 Oct 2025 09:29:02 +0200 Subject: [PATCH] Auto update --- compare.html | 53 +++++++++++++++++++++++----------------------------- 1 file changed, 23 insertions(+), 30 deletions(-) diff --git a/compare.html b/compare.html index e52846f4..e966e695 100644 --- a/compare.html +++ b/compare.html @@ -54,35 +54,30 @@

-SnapRAID is only one of the available not standard RAID solutions for disk arrays. +SnapRAID is just one of many RAID-like solutions available for disk arrays.

-The best known others are: +Some of the best-known alternatives include:

@@ -153,7 +148,7 @@ New Storage Spaces adds Dual Parity if you have at least 7 disks https://blogs.technet.microsoft.com/tip_of_the_day/2014/07/23/tip-of-the-day-dual-parity-storage-spaces/ --> -Other failures
If more disks fail than the supported redundancy model, +More disk failures
If more disks fail than the supported redundancy model, is it possible to recover the data in the not failed disks? YesYesNoNoNo @@ -207,18 +202,16 @@ the parity is automatically recomputed, making impossible to recover the silent

-[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. +[3] - ZFS and Btrfs provide bit-rot protection comparable to SnapRAID, always verifying data before use. +In this regard, all 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. +One drawback of ZFS is that the default Fletcher checksum prioritizes speed over reliability. +Even though it is a 256-bit checksum, Fletcher is generally considered weak. Similarly, Btrfs uses CRC32C by default, which is strong, but ony 32 bits. +A better alternative is "edonr" for ZFS and "xxhash" for Btrfs. +In contrast, SnapRAID uses the 128-bit SpookyHash, +which provides state-of-the-art checksum quality without compromising speed.
-ZFS also uses a sub-optimal RAID-Z3 algorithm, that requires double computations than the equivalent SnapRAID's z-parity. +ZFS also employs a sub-optimal RAID-Z3 algorithm that requires roughly twice the computation compared to SnapRAID’s z-parity.