The birth (or death) of a relative, the release of a new program, game, series, movie, the date you were dreaming about, could be anything

    • linucs@lemmy.mlOP
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      Is it really going to be that huge? I’m using btrfs, how is bcachefs better?

      • arirr@lemmy.kde.social
        link
        fedilink
        arrow-up
        4
        ·
        5 months ago

        It has most of the major features of BTRFS + tiered storage + per file/directory redundancy + native encryption support. It also seems to be architectured in a way that avoids the write-hole issue for RAID 5/6 that BTRFS has and therefore once that feature is added, it won’t be as likely to eat your data. It also had a better system for handling different sized drives.

        Overall, it seems like a redesigned BTRFS with the experience of bcache development and benefit of hindsight avoiding some of the early pitfalls that BTRFS had. It already seems like the ideal filesystem that does it all for single systems. Especially if Kent gets the backing he needs to fill out the rest of the roadmap, I really don’t see what other filesystems have to offer that are worth losing the other benefits.

        Maybe I’m wrong and it will stall or something, but it has been almost a decade already and there have been steady improvements throughout. I plan to switch to it as soon as I can get it working. It is still a bit rough getting a proper multi-drive encrypted system booting since it is still early days of mainline support and disros don’t have very good support for it yet.