Kent Overstreet hasn't been idle , as he recently announced a decisive step in the evolution of his file system: from now on, it will be distributed via DKMS (Dynamic Kernel Module Support). With this approach, the Bcachefs module is delivered as source code and is automatically compiled on the user's system after the package is installed, transparently rebuilding itself each time the Linux kernel is updated.
This change eliminates the dependency on direct inclusion in the main kernel, allowing Bcachefs to be kept up-to-date independently. For users, the experience will be virtually identical, as they can even continue using this filesystem as root thanks to the inclusion of DKMS modules in the initramfs.
As many of you probably know, bcachefs is switching to shipping as
a DKMS module. Once the DKMS packages are installed, very little should
change for end users, but we have work to do in distribution
side of things to make sure everything goes smoothly.
Support for distributions and long-term maintenance
One of the most important aspects of this move is the support of major distributions. Overstreet confirmed conversations with the Debian and openSUSE teams, who had considered disabling Bcachefs support in their kernels for fear of future abandonment. However, thanks to the transition to DKMS, the disabling has been postponed until the packages are ready.
Meanwhile, the user and developer community has been actively involved in ensuring a smooth packaging and distribution process. Arch Linux, NixOS, and Fedora already have a strong track record of supporting Bcachefs tools and modules, while Debian is working on reintroducing the previously abandoned bcachefs-tools package.
Since its inclusion in kernel 6.16, Bcachefs has shown remarkable stability, with only minor bugs reported. Most of the issues detected have been low-impact, related to performance or internal testing, without affecting end users. This reinforces the project's decision to soon remove the "experimental" label that still accompanies the file system.
Overstreet emphasized that version 6.16 has been a solid foundation for thousands of users , and although the integration process using DKMS will take time, the widespread adoption of this solution will ensure continuity and stability while the packaging details are fine-tuned for each distribution.
It's worth noting that the removal of Bcachefs doesn't mean the project can't be readmitted . For now, it will have to demonstrate its ability to contribute constructively, respecting the established rules and processes of the Linux kernel ecosystem. Only then will the possibility of reopening active file system integration within the main kernel be considered.
This move doesn't eliminate Bcachefs' presence in Linux, but it does send a clear signal about the importance of collaboration and community development dynamics. While Bcachefs has been enthusiastically received for its technical features, such as its combination of performance and advanced features, its future in the kernel will depend on both the robustness of its code and its developer's ability to work collaboratively with the rest of the community.
And it is precisely because of this aspect that the development of Bcachefs may have a second chance, as it has been supported by an active community that participates in testing, reports bugs, and collaborates on debugging. According to Overstreet, this collaborative effort has allowed them to consolidate the system's stability and accelerate its transition to a more flexible distribution model.
Finally, it is mentioned that the next challenge will be ensuring the proper integration of bcachefs-tools across all distributions and encouraging the participation of packagers and testers. With this, the project is on track to become a mature, production-ready alternative within the Linux ecosystem.
If you are interested in learning more, you can find the details at the following link.