From 6a5c48a858b48bdd8e908f707a6ea50d249ba2fb Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Tue, 14 Oct 2025 11:14:51 +0200 Subject: [PATCH] Auto update --- compare.html | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/compare.html b/compare.html index 58ac558d..e4ea35dd 100644 --- a/compare.html +++ b/compare.html @@ -179,8 +179,11 @@ http://www.eecs.berkeley.edu/Pubs/TechRpts/1987/5853.html

Notes

-[1] - unRAID lacks native checksums and ignores silent errors. If a parity error results from a silent data error, the parity is automatically recomputed, making it impossible to recover the silent error, even manually. -To get a similar functionality of SnapRAID, you have to use the Btrfs filesystems for all your data disks. +[1] - unRAID lacks native checksums and ignores silent errors. +Even worse, if a parity mismatch is detected due to a silent error in the data, +the parity is automatically recomputed, making it impossible to recover the silent error, even manually. +Integrity checksum plugins do not help in this case, as they are not integrated into the parity-checking process. +To achieve functionality similar to SnapRAID, you would need to use the Btrfs filesystem for all your data disks.

@@ -211,7 +214,7 @@ ZFS also employs a suboptimal RAID-Z3 algorithm that requires roughly twice the [8] - unRAID can use integrity checksums via plugins like Dynamix File Integrity, or bunker. However, these are independent of parity processing and not used to aid recovery. For example, when recovering a single failed disk with dual parity, checksums can identify additional silent errors to facilitate recovery. -To get a similar functionality of SnapRAID, you have to use the Btrfs filesystems for all your data disks. +To achieve functionality similar to SnapRAID, you would need to use the Btrfs filesystem for all your data disks.