BTRFS Raid10 can seemlessly cpmbole multiple raw disks without trying to match capacity. Next time I just replace my 4T disk in my 5 disk Raid10 with 20T. Curr

BTRFS Raid10 can seemlessly cpmbole multiple raw disks without trying to match capacity. Next time I just replace my 4T disk in my 5 disk Raid10 with 20T. Currently I have 4+8+8+16+20 disks. MD raid does not do checksumming. Although I believe XFS is about to add support for it in the future. I have had my BTRFS raid filesystem survive a lot during the past 14 years: - burned power: no loss of data - failed ram that started corrupting memory: after a little hack 1) BTRFS scrub saved most of data even though the situation got so bad kernel would crash in 10 minutes - buggy pcie SATA extension card: I tried to add 6th disk, but noticed after fee million write errors to one disk that it just randomly stopped passing data through: no data corruption, although btrfs write error counters are in 10s of millions now - 4 disk failures: I have only one original disk still running and it is showing a lot of bad sectors 1) one of the corrupted sectors was in the btrfs tree that contains the checksums for rest of the filesystem and both copies were broken. It prevented access to some 200 files. I patched the kernel to log the exact sector in addition to the expected and actual value. Turns our it was just a single bit flip. So I used hex editor to flip it back to correct value and got the files back