‹ BackHN Continuity

Thread

Btrfs/ZFS/bcachefs under workloads classic benchmarks skip

179 points · 190 comments · farlight

  1. skerit · · focus · HN ↗
    Oh, so bcachefs is doing pretty well.
    1. tarruda · · focus · HN ↗
      Except for the fact that the developer has sabotaged the project into being removed from mainline?
      1. irusensei · · focus · HN ↗
        That might be the best thing happened to the project since now development can happen at its own pace without the clicky bait influencers.

        In fact they delivered the erasure coding for parity raid back in march this year.

        The thing is that as soon as you seriously give a chance to Bcachefs you see how good it is. I can only tell you that mixing different device tiers and having a per-file/directory replication setting is a god send specially in these times where storage costs more than gold.

        1. tarruda · · focus · HN ↗
          > The thing is that as soon as you seriously give a chance to Bcachefs you see how good it is.

          I'm pretty sure Bcachefs is amazing and better than Btrfs. I also think Zfs is amazing and better than Btrfs. Even so, I still use Btrfs because I know it is guaranteed to always be present on any Linux without any effort on my part.

          > That might be the best thing happened to the project since now development can happen at its own pace without the clicky bait influencers.

          A better approach might have been to just paused mainline merging instead of forcing being kicked out?

          Eg "Hey Linus, Bcachefs is still in early development and I need to merge changes in a pace that is not compatible with Linux development process. So I'm going to pause for a while now and once it reaches maintenance status I will focus on submitting patches in a healthy pace that you can digest".

          1. ssl-3 · · focus · HN ↗
            > I still use Btrfs because I know it is guaranteed to always be present on any Linux without any effort on my part.

            I used to think that about ReiserFS, too. It was in the mainline kernel, development was snappy, and it solved some performance problems. I used it all over the place.

            Things then subsequently... changed. :-/

            1. bjoli · · focus · HN ↗
              You had plenty of time to move away from reiserfs. Something like 15 years between the conviction and removal.
              1. ssl-3 · · focus · HN ↗
                I did.

                And I did move away from it.

                But I had once expected ReiserFS to be permanent, especially since this Hans Raiser dude who was driving the ship seemed to be sharp AF, and this seemed doubly-true when his filesystem got mainlined.

                But it was not permanent. It did not last forever.

                This idea of permanence, or rather the lack of it, was the whole of the point that I was responding to and also trying to impress upon.

                At the end of the day: We do not know the future. Things can change.

                I've outlived this one high-performance Linux filesystem in my life that I was using. This does not in any way mean that I will be the last to outlive other Linux filesystems.

                Permanence is not guaranteed.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.