Allow users to choose between native Btrfs RAID and mdadm-based RAID, with clear explanations in the control panel about the advantages, limitations, and ideal use cases for each method.
_____________________________________________________________________________________________________________________
Native Btrfs RAID
- Provide all RAID configurations supported by Btrfs, including RAID 0, 1, 10, 5, 6, 1C3, and 1C4.
- Allow independent RAID configuration for data and metadata when necessary.
- For stable levels such as RAID1 and RAID10, maintain the same redundancy structure for both data and metadata.
- For levels more prone to the write hole issue (such as RAID5/6), apply RAID1C3 or RAID1C4 for metadata by default, ensuring integrity, fault tolerance, and protection against data corruption.
- Examples of safe combinations (DATA-METADATA): RAID5-1C3, RAID5-1C4, and RAID6-1C4.
- The native Btrfs RAID provides superior protection against bit rot, automatic error detection and correction, and data integrity features comparable to ZFS.
- The native Btrfs RAID is generally more reliable and secure than mdadm, even in configurations such as RAID5-1C3 or RAID6-1C4. For this reason, it is recommended primarily for advanced users who seek higher data integrity and finer control over RAID behavior.
- Offer as an option for users who prioritize simplicity and traditional compatibility.
- Indicate in the control panel that this mode does not provide advanced integrity or self-healing features, but is well-tested and proven stable after decades of use in Linux environments.
Monitoring and Maintenance
Display detailed RAID array status, including:
- Progress and estimated rebuild time
- Checksum integrity
- Start Scrub
- Executing Balance
- Performing Integrity Check
- Starting Manual Rebuild
Perhaps one day: Offer ZFS support in the future.
