BCacheFS thread

[LiKenun]

For me, personally, the draw is that it aims to solve a few problems not solved by any other file systems (not even ZFS):

• Read/write cache (promote/foreground targets)
• Elimination of the RAID write hole problem
• Tiering compression and RAID levels: recognizing that compression and erasure coding is detrimental to high performance, bcachefs introduces the concept of compressing and erasure coding data written to background devices while metadata, read, and write caches remain uncompressed and mirrored for performance.

There’s also this:

@WynnSmith

The trouble is, while ZFS fixes the problem of correctly managing storage spaces so we’re not continually reconfiguring partitions and drives, it introduces a new challenge of making Day-one decisions for the initial build which can’t be reversed without equivalent pain.

btrfs doesn’t have this problem, but suffers from a few other dealbreakers.

@ulzeraj

High performance, low tail latency

I’m curious as to how this pans out in real workloads.