RAIDZ2 vs RAIDZ3
What Is the Difference Between RAIDZ2 and RAIDZ3?
RAIDZ2 uses two parity components and can tolerate up to two device failures within the RAIDZ VDEV. RAIDZ3 uses three parity components and can tolerate up to three device failures within the VDEV.
RAIDZ2 therefore provides better usable-capacity efficiency for the same number and size of drives, while RAIDZ3 sacrifices another drive-equivalent of capacity for an additional level of fault tolerance.
RAIDZ2 vs RAIDZ3 at a Glance
| Feature | RAIDZ2 | RAIDZ3 |
|---|---|---|
| Parity Level | Double Parity | Triple Parity |
| Device Failures Tolerated | Up to 2 | Up to 3 |
| Minimum Technical Drive Count | 3 | 4 |
| Parity Capacity Cost | 2 drive-equivalents | 3 drive-equivalents |
| Usable Capacity | Higher at same drive count | Lower at same drive count |
| Fault Tolerance | High | Higher |
| Typical Design Priority | Balance redundancy and capacity | Maximum parity protection |
Double Parity vs Triple Parity
Both RAIDZ2 and RAIDZ3 distribute data and parity across the devices in the RAIDZ VDEV. The defining difference is the number of parity components maintained for each RAIDZ stripe.
RAIDZ2 can reconstruct data after as many as two device failures within the VDEV.
RAIDZ3 adds another parity level and can reconstruct data after as many as three device failures within the VDEV.
How RAIDZ2 and RAIDZ3 Use Parity
The examples below use eight equal-size drives to illustrate the capacity tradeoff. They are simplified planning models rather than literal representations of every RAIDZ stripe written by ZFS.
RAIDZ2
RAIDZ3
RAIDZ2 vs RAIDZ3 Usable Capacity
For a simplified capacity estimate using equal-size drives, RAIDZ usable capacity can be approximated by subtracting the parity level from the number of devices and multiplying the result by the capacity of the smallest device.
These formulas are simplified raw-capacity estimates. Actual usable filesystem space is affected by drive capacity reporting, RAIDZ allocation behavior, metadata, record sizes, reserved free space and other ZFS overhead.
Capacity Difference With Equal-Size Drives
| Configuration | Raw Capacity | RAIDZ2 Approx. | RAIDZ3 Approx. | Difference |
|---|---|---|---|---|
| 6 × 8 TB | 48 TB | ~32 TB | ~24 TB | ~8 TB |
| 8 × 12 TB | 96 TB | ~72 TB | ~60 TB | ~12 TB |
| 10 × 16 TB | 160 TB | ~128 TB | ~112 TB | ~16 TB |
| 12 × 20 TB | 240 TB | ~200 TB | ~180 TB | ~20 TB |
Simplified decimal capacity examples for comparison only. Actual ZFS-reported usable capacity will differ.
RAIDZ3 Provides One Additional Failure Tolerance
RAIDZ2 remains operational with as many as two failed devices in the VDEV. RAIDZ3 extends that protection to three failed devices.
Why Would You Need Triple Parity?
The value of RAIDZ3 is not simply that three drives might fail simultaneously. The additional parity also provides another margin of protection while the VDEV is already operating in a degraded state and a failed device is being replaced or data is being reconstructed.
This can become more important in storage systems containing large-capacity drives, wide VDEVs, long recovery windows or data for which additional availability protection justifies the capacity cost.
RAIDZ2 vs RAIDZ3 Performance
Performance differences cannot be reduced to parity count alone. VDEV width, drive type, record size, workload, compression, hardware and the number of top-level VDEVs can all affect real-world ZFS performance.
RAIDZ2 vs RAIDZ3 During a Degraded State
When a device fails, the VDEV loses one level of its available failure margin until redundancy is restored. This is where the practical difference between RAIDZ2 and RAIDZ3 becomes especially important.
When RAIDZ2 May Be the Better Choice
RAIDZ2 is often attractive when the goal is strong multi-drive fault tolerance without dedicating a third drive-equivalent of every VDEV to parity.
When RAIDZ3 May Be the Better Choice
RAIDZ3 becomes attractive when the additional protection provided by triple parity is more important than maximizing usable capacity.
RAIDZ2 or RAIDZ3?
| Priority | Likely Direction | Why |
|---|---|---|
| More usable capacity | RAIDZ2 | One fewer parity-equivalent than RAIDZ3 |
| Maximum parity protection | RAIDZ3 | Can tolerate a third device failure |
| Balance capacity and redundancy | RAIDZ2 | Double parity with better capacity efficiency |
| Extra degraded-state margin | RAIDZ3 | Additional parity remains available after failures |
| Capacity-focused archive | Often RAIDZ2 | More capacity per equal-width VDEV |
| Very high redundancy priority | Often RAIDZ3 | Triple parity provides another failure margin |
RAIDZ3 Is Not Automatically Better Than RAIDZ2
RAIDZ3 provides greater device-failure tolerance, but that does not make it the correct layout for every ZFS pool. The third parity level consumes additional storage capacity, and the complete pool design must account for workload, VDEV width, performance requirements, expansion strategy, hardware and recovery objectives.
The best RAIDZ level is the one that meets the system's actual capacity, performance and failure-tolerance requirements rather than simply providing the largest parity count.
Neither RAIDZ2 nor RAIDZ3 Replaces Backups
RAIDZ2 and RAIDZ3 provide storage redundancy against specified device failures. They do not create an independent backup of the data. Important information should still be protected by an appropriate backup and recovery strategy.
RAIDZ2 vs RAIDZ3 FAQ
What is the main difference between RAIDZ2 and RAIDZ3?
RAIDZ2 uses double parity and can tolerate up to two failed devices. RAIDZ3 uses triple parity and can tolerate up to three.
Does RAIDZ3 provide more redundancy?
Yes. RAIDZ3 provides one additional parity level and one additional device-failure tolerance compared with RAIDZ2.
Does RAIDZ2 provide more usable capacity?
Yes, when comparing equal drive counts and capacities. RAIDZ2 uses two parity-equivalents while RAIDZ3 uses three.
How many drives can RAIDZ2 lose?
A RAIDZ2 VDEV can tolerate up to two device failures without losing its data.
How many drives can RAIDZ3 lose?
A RAIDZ3 VDEV can tolerate up to three device failures without losing its data.
Is RAIDZ3 always safer than RAIDZ2?
RAIDZ3 provides greater device-failure tolerance, but overall data protection also depends on pool design, operational practices and independent backups.
Is RAIDZ3 worth the capacity loss?
It can be when the additional failure margin is more valuable than the capacity consumed by the third parity level.
Which is better for large drives?
Large drive size alone does not determine the correct layout. Recovery time, VDEV width, capacity requirements and acceptable failure risk should all be considered.
Is RAIDZ2 similar to RAID 6?
RAIDZ2 and RAID 6 both use double-parity concepts, but RAIDZ is part of ZFS and has different storage, allocation and data-integrity behavior.
Are RAIDZ2 and RAIDZ3 backups?
No. Both provide redundancy, but neither replaces an independent backup strategy.