Thread

Btrfs/ZFS/bcachefs under workloads classic benchmarks skip

179 points · 190 comments · farlight

gdgghhhhh · 1789885476 · focus · HN ↗
In case someone wonders why bcachefs is sadly no longer part of the mainline kernel. Start reading here: <a href="https://lwn.net/Articles/1027289/" rel="nofollow">https://lwn.net/Articles/1027289/
1. lifty · 1789896697 · focus · HN ↗
  Is there any chance bcachefs will be included again in the future?
  1. gdgghhhhh · 1789896845 · focus · HN ↗
    I'm optimistic.
    doubletwoyou · 1789899854 · focus · HN ↗
    Sir Overstreet still seems insistent on having done no wrong on account of fixing user bugs taking priority over literally everything, so clearly there’s a mindset clash that’s gonna prevent a re-merging unless that Torvalds decides to change the same procedure he’s been doing for the past 2 decades or Overstreet knocks his own ego down a peg.
    Edit: I think this makes for some good reading: <a href="https://lkml.org/lkml/2025/8/9/427" rel="nofollow">https://lkml.org/lkml/2025/8/9/427
    gdgghhhhh · 1789902757 · focus · HN ↗
    The key is forming a team of maintainers.
    koverstreet · 1789990491 · focus · HN ↗
    If you want to be a filesystem maintainer, you start out by doing the work involved.
    I'm afraid not all opinions are created equal, this isn't design by committee :)
    MBCook · 1789922242 · focus · HN ↗
    I’ve been following kernel development for something like three years using LWN and other sources.
    I can’t remember anyone earning the level of hostile treatment he did and getting kicked out.
    I don’t see how it would ever happen.
    locknitpicker · 1789972691 · focus · HN ↗
    > I can’t remember anyone earning the level of hostile treatment he did and getting kicked out.
    You don't seem to be following it very closely, as apparently you failed to come across the history of abuse and hostile behavior of bcachefs's maintainer.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.