3 ms·
Btrfs people have been telling everyone that RAID5/6 code is incomplete for years now, so hopefully people weren't depending on it for important things. The wi
by sp332 10y ago
Btrfs people have been telling everyone that RAID5/6 code is incomplete for years now, so hopefully people weren't depending on it for important things. The wiki link is broken, here's the page https://btrfs.wiki.kernel.org/index.php/RAID56 https://btrfs.wiki.kernel.org/index.php/RAID56 and you can see in the history that on the very first version of the page, in the first sentence, "the recovery and rebuild code isn't bulletproof or complete yet."
- pantalaimon 10y agoThis warning has only been added recently https://btrfs.wiki.kernel.org/index.php?title=RAID56&diff=30445&oldid=29769 https://btrfs.wiki.kernel.org/index.php?title=RAID56&diff=30...
- sp332 10y agoOh, so that's ~7 months of people maybe using it for important things. That could be really bad then.
- pantalaimon 10y agoWell that line about it stabilizing over the next couple of kernel releases was added in February 2015, so when I installed Ubuntu 16.04 on my NAS I thought things probably had calmed down sufficiently. As I learned the hard way, I was wrong and that warning is very much justified. https://btrfs.wiki.kernel.org/index.php?title=RAID56&diff=29294&oldid=25681 https://btrfs.wiki.kernel.org/index.php?title=RAID56&diff=29...
- sp332 10y agoWell, I have a problem with a btrfs RAID1 (which isn't really RAID1 but whatever) where if I read certain files my kernel crashes. So that's fun too.
- rleigh 10y agoBetter that than the unrecoverable dataloss I suffered (it trashed both disks... and also panicked the kernel). In fact, they were so screwed it panicked the system on every boot until I booted with a non-Btrfs-supporting kernel and blanked them with dd...