What is triple parity RAID-Z3?
In the world of high-capacity storage, the "RAID-5 is dead" argument stems from a simple reality: as hard drives get larger, the time it takes to rebuild a failed disk increases. During that long rebuild window, a second disk failure would mean total data loss.
RAID-Z3 is the ZFS answer to this "statistical nightmare." It is a triple-parity scheme that allows a storage pool to survive the simultaneous failure of up to three physical disks without losing a single byte of data.
Traditional RAID (like RAID-5) uses one parity block. RAID-6 (and RAID-Z2) uses two. RAID-Z3 raises the stakes by calculating three distinct types of parity for every stripe of data.
When data is written to a RAID-Z3 vdev:
The data is divided into chunks.
ZFS calculates three different parity sets (using complex Galois field mathematics).
These parity blocks are distributed across all disks in the set.
Even if three disks disappear at the exact same moment—or, more likely, if one disk fails and two more develop "unrecoverable read errors" during the rebuild—ZFS can use the remaining parity and data to mathematically reconstruct the missing information.
In the era of 20TB+ hard drives, RAID-Z3 isn't "overkill"—it's insurance.
The Rebuild Window: Rebuilding a 20TB drive can take days or even weeks. During this time, the remaining drives are under intense "read stress."
The URE Risk: Large drives have a statistical probability of Unrecoverable Read Errors (URE). If you have a 10-disk RAID-Z2 array and one disk fails, you can only afford one more error. If a second disk fails AND a third disk has a tiny URE during the rebuild, your pool is compromised.
RAID-Z3 provides the "buffer" needed to survive a catastrophic failure followed by minor errors on other disks.
There is no "free lunch" in storage. The extra safety of RAID-Z3 comes with specific costs:
| Resource | Impact |
| Storage Efficiency | You lose the capacity of 3 disks per vdev. In an 8-disk array, only 5 disks provide usable space. |
| Write Penalty | The CPU must calculate three different parity equations for every write. This is more computationally expensive than RAID-Z1 or Z2. |
| IOPS | Like all RAID-Z levels, the random I/O performance (IOPS) of the entire vdev is roughly equivalent to the IOPS of a single disk. |
Because of the three-disk overhead, RAID-Z3 is best used in "wide" configurations where the efficiency loss is less painful.
Ideal Array Size: 11 to 15 disks. At this width, losing 3 disks to parity still leaves 8–12 disks for data, striking a balance between safety and cost.
Workload: High-capacity archival, backup targets, and large-scale media storage.
Avoid: Small pools (e.g., a 5-disk RAID-Z3 only gives you the space of 2 disks, which is highly inefficient).
[Image comparing storage efficiency of RAID-Z1, RAID-Z2, and RAID-Z3]
| Feature | RAID-Z2 (Double Parity) | RAID-Z3 (Triple Parity) |
| Fault Tolerance | 2 Disks. | 3 Disks. |
| Risk of Data Loss | Low (safe for medium drives). | Ultra-Low (safe for 20TB+ drives). |
| CPU Overhead | Moderate. | Higher. |
| Recommended Use | General business storage. | Massive data hoards / Cold storage. |
RAID-Z3 is the ultimate "safety net" for the era of giant hard drives. While it costs you more in hardware (the three-disk "tax"), it provides a level of peace of mind that RAID-Z1 or Z2 simply cannot match when dealing with multi-terabyte rebuild times.