Thread

Btrfs/ZFS/bcachefs under workloads classic benchmarks skip

179 points · 190 comments · farlight

irusensei · 1789848737 · focus · HN ↗
BCacheFS is the best Linux filesystem now that storage costs a premium.
You can mix devices of different sizes and types on bcachefs. You can have foreground and background devices to balance performance and also different compression settings for foreground and background transactions.
You can set replicas=N to the individual file or directory on bcachefs. For example files you can just re-download or re-build. Likewise you can set a higher number of copies to important files.
1. lukaslalinsky · 1789883162 · focus · HN ↗
  I've been using ZFS on my Linux servers for years and have pretty good experience with it. I've not been following Linux development too much. Is bcachefs usable/stable/reliable enough to replace it?
  1. khajdamowicz · 1789885150 · focus · HN ↗
    It's not as battle-tested like ZFS with 15+ years of field usage, but it's good enough for me and other users.
    There's a NAS appliance called NASty and it shares publicly usage stats: <a href="https://nasty-telemetry.pages.dev/" rel="nofollow">https://nasty-telemetry.pages.dev/ Those numbers are NASty alone. There are more users on other systems.
    cromka · 1789898773 · focus · HN ↗
    15+ years of ZFS code is also often said as being a nearly unmanageable pile of mess, supposedly to the point that there’s some of the code that maintainers are afraid of touching, and with plenty of unresolved weird bugs (which I experienced myself with data loss).
    Sometimes starting fresh with one coherent codebase and all features design baked in from the start might be better.
    lukaslalinsky · 1789973134 · focus · HN ↗
    It takes 10+ years for any storage engine to iron out all the wrinkles, get it to a state where it's both fast enough, and you can trust it to not lose data. It's stupid to throw it away once it reaches that point.
    cromka · 1789988072 · focus · HN ↗
    It's not stupid if the 10+ years code is unmaintainable. Why did you ignore that part?

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.