@shibao@Moon@feinzer btrfs had a bug in their raid code that destroyed data, years after the code functionality was marked stable. At least by now zfs is a thing everywhere so there's no need to even look at btrfs.
@feinzer@ak.airis.work this conversation only brought up again cuz moon mentioned like 5-6 catastropic data loss from brtfs and (afaik) lall's database getting corrupted while also on top of brtfs, but yeah maybe this is all just anecdotal and very skewed but idk
Btrfs probably runs fine for 99% of users so I don't think there's much of a need so switch away from it if you're already using it, but I can't find a good reason to use it on a new system.
@lain@lain.com@Moon@shitposter.club@feinzer@ak.airis.work to me it feels like apache vs nginx, like it's basically the same for most cases except the extreme slim chance where you get a vulnerability or something apache just has 10x more for no reason or whatever, except worse with filesystems cuz permanent
@Moon@shitposter.club@lain@lain.com@feinzer@ak.airis.work i just remember seeing a comparison of reported cves for apache vs nginx over the last x years but i can't find it at all so it might be hearsay i also remember something about the codebase size being an order of magnitude different but idk