‹ BackHN Continuity

Thread

Btrfs/ZFS/bcachefs under workloads classic benchmarks skip

179 points · 190 comments · farlight

  1. lproven · · focus · HN ↗
    Interesting although I'd have liked more summaries: there's an awful lot there.

    But the reasons I choose filesystems are more about reliability, failure modes, surrounding tooling, and so on.

    Btrfs fails in several critical areas:

    1. No way to accurately find free space

    2. catastrophic failure on write if a volume fills up, the probability of which is greater because of #1

    3. repair tools usually do not recover a corrupted volume and in my testing are most likely to render as damaged volume completely unreadable, which makes #2 worse

    Put these things together and I can never trust Btrfs again. In the 9 years since I encountered these, I see no effort to fix them, just fooling around witg unimportant side details like performance tweaks.

    Fix the critical issues first then make it faster.

    1. KrOctave · · focus · HN ↗
      This is why I have fully switched to Bcachefs, which is just way more stable and performant than btrfs
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.