From ba3e8d77b43d18565355d296bf3ddde6956a8357 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Fri, 31 Oct 2025 09:59:12 +0100 Subject: [PATCH] Auto update --- compare.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compare.html b/compare.html index 09a9f15c..dfea8410 100644 --- a/compare.html +++ b/compare.html @@ -200,7 +200,7 @@ ZFS also employs a suboptimal RAID-Z3 algorithm that requires roughly twice the

-[4] - unRAID completely rebuilds parity when adding a new disk that already contains data, and during this process the existing data in the array is not protected. +[4] - unRAID completely rebuilds parity when adding a new disk that already contains data, and during this process the existing data in the array is not protected. This is a serious flaw, as a full parity rebuild puts considerable stress on all drives. If any disk is near failure, there’s a high risk it could fail during this operation. The only safe way to add a new data disk is to pre-clear it first.