which is "better", XFS or BTRFS? i only care about file system resilience on shitty SSDs, so like, which one is going to be slower at letting my photos be randomly destroyed by bit flips? #linux
@aeva it won't make any difference, neither has any special resilience mechanisms (especially not for data at rest).
@dotstdy well butts
@aeva @dotstdy not true for btrfs? btrfs dup can be used for a raid configuration or on a single disk if you want, although obviously that won't help you if the whole device goes bad
@glyph @aeva I mean you can set up lots of wild configurations yea. I just mean without having some form of parity or raid they're not going to be any different in themselves (and you can do raid with either one). And you can potentially just store parity data with the files you want to archive if you just want a single disk option.
@dotstdy @aeva is there a tool for maintaining and scrubbing parity data? if I wanted this I would definitely have a scheduled "btrfs scrub" on a DUP=2 volume as just … the most ergonomic way to get parity data that I didn't have to manually babysit
@glyph @aeva well it depends on the use case, if it's data at rest you can potentially manually generate parity data (ye old par archives anyone?) without any FS level features at all. But if you want to have an automatic process for protecting stuff then it might be more involved yeah.

@dotstdy @aeva I've never heard of a 'par archive' so no I don't know :).

I mean I could easily write code to generate parity data, and even to apply it; but btrfs will automatically generate it, verify it, apply parity back to the original data and move it to a different physical sector on the disk when doing that application, which I'm sure I could figure out in a months-long engineering project, but, why? :)