What does bcachefs do better than BTRFS or ZFS?

Than both? Tiered storage. Than btrfs? Hopefully parity RAID, and performance. Than ZFS? Being GPL compliant, so viable for being in-tree in the Kernel.

(list most likely incomplete)

Near future? Its been in development for 7 years and still hasnt been accepted upstream (an upstreaming effort is in progress, though).

It's just silliness (attitudes, versus technical merit) blocking it now. The only thing stopping it is if something happens to Kent.

https://www.phoronix.com/news/Linux-Torvalds-Bcachefs-Review

Any tldr about why we should be looking forward to this?

Any cool things?

Erasure Coding when it lands should be pretty solid.

Until then per-directory data replicas is the killer feature for me (Music has 3, Documents has 5, Downloads has 1). Something to be very excited about with full compression and encryption.

You can do that with ZFS at the cost of defining separate filesystems per directory.

I don't use multiple replicas, but I use that to tailor my backups per directory. ~/documents is snapshotted and backed up on the regular, with long-lived snapshots. Code is snapshotted regularly, but snapshots don't live too long, and they're not shipped to a different drive. I don't care for ~/tmp so no snapshots.

---

edit: the cost, besides having to actually create the file systems, is that moving data between them isn't instant.

> the cost, besides having to actually create the file systems, is that moving data between them isn't instant.

No more the case after block cloning support goes production: https://github.com/openzfs/zfs/pull/13392

Nice, thanks!