• Chewy@discuss.tchncs.de
    15·
    10 months ago

    The company that’s been funding bcachefs for the past 6 years has, unfortunately, been hit by a business downturn - they’ve been affected by the strikes in the media production industry. As such, I’m now having to look for new funding.

    Hopefully they find a new company to fund the development of bcachefs. Btrfs has major funding from facebook and others, so hopefully there’ll be interest in bcachefs since it has some interesting features over btrfs (namely caching and configurable data placement).

    • d3Xt3r@lemmy.nzM
      16·
      10 months ago

      You’re right, there isn’t any special effort put towards wear leveling, but the bcache FAQ (NOT bcachefs mind you, but the same should be applicable) mentions this:

      #I thought SSDs wore out quickly if you did regular writes to them?

      For older SSDs, that was true. Newer SSDs will recognize that a given block is getting heavy writes and will actually swap a heavily written block with a more lightly written block (moving the data transparently and using internal pointers to keep track of the move). This is called “wear leveling” and its use can take a drive whose individual blocks might have tens of thousands of writes before failure and produce an SSD that can support up to millions of writes in a given location by moving data around underneath. Also, keep in mind that unlike (most) standard filesystems that treat SSDs as random access devices that can take any number of writes of any size, bcache understands the write issues in SSDs and tunes its write algorithms to minimize the number of erasures needed. As a side note, what we think of as ‘‘write’’ performance problems on SSDs are largely ‘‘erase’’ performance problems.

    • DaPorkchop_@lemmy.mlOP
      1·
      9 months ago

      Yeah, although the neat part is that you can configure how much replication it uses on a per-file basis: for example, you can set your personal photos to be replicated three times, but have a tmp directory with no replication at all on the same filesystem.

        • DaPorkchop_@lemmy.mlOP
          1·
          9 months ago

          What exactly are you referring to? It seems to me to be pretty competitive with both ZFS and btrfs, in terms of supported features. It also has a lot of unique stuff, like being able to set drives/redundancy level/parity level/cache policy (among other things) per-directory or per-file, which I don’t think any of the other mainstream CoW filesystems can do.