LSF topic: bcachefs status & roadmap I'd like to make this as open ended as possible; I'll talk a bit about current status and work on the technical innards, but I want the focus to be more on - gathering ideas for the roadmap - what we can do to make it easier for poeple to contribtue - finding out what people are interested in - general brainstorming Status wise: things are stabilizing nicely (knock on wood, 6.7 about to come out and then we really find out how well I've done); CI test failures slowly but steadily declining and user reported bugs are getting fixed quickly and easily. Some performance stuff to investigate still - we're still slower than we ought to be on certain metadata workloads, haven't lokoed at why yet; fsck times can be slow on very large filesystems, and we know what needs to be addressed there - but users seem to be pretty happy with scalability past the 100 TB mark. A good chunk of online fsck is landing in 6.8 - fully functional for the passes that are supported. Disk space accounting rewrite is well underway - huge project but the main challenges have been solved, when that's done we'll be able to add per snapshot ID accounting, as well as per compression type accounting, and it'll be a lot easier to add new counters. Some cool forwards compat stuff just landed (bch_sb_downgrade section; tells older versions what to do if they mount a newer filesystem that needs fsck to use). A delayed allocation for btree nodes mode is coming, which is the main piece needed for ZNS support Further off: some super fancy autotiering stuff is getting designed (we should eventually be able to track data hotness on on an inode:offset basis, which will eventually let us use more than 2 performance tiers of devices). Erasure coding will finally be getting stabilized post disk space accounting rewrite (which solves some annoying corner cases). Cheers, Kent
