BCacheFS Evolves: A New DKMS Module Following its Move Away from the Linux Kernel

by

The BCacheFS file system, known for its technical innovations in Linux storage management, is seeing its future reconfigured with its removal from the main Linux kernel. In the face of tensions on the kernel mailing list, decisions made by Linus Torvalds have led to a significant repositioning: BCacheFS will now be offered as a Dynamic Kernel Module Support (DKMS) module. This development has major implications for Linux users and distributions that leverage this growing file system. After years of gradual integration with promises of robustness and advanced features, this shift reflects the challenges of balancing technical ambition with staying in line with the expectations of the kernel community. However, managing the module via DKMS offers an alternative, independent maintenance path, allowing BCacheFS to continue to be used by enthusiasts and administrators seeking performance and flexibility in open source storage under Linux. BCacheFS in the Linux Ecosystem: Why Its Removal from the Linux Kernel Is a Major Turning Point

The Linux kernel, the heart of all Linux distributions, is an ecosystem where each module or file system must meet strict stability and maintenance criteria. BCacheFS stood out in particular for its innovative approach to copy-on-write (COW), integrating advanced features such as native encryption, transparent compression, and atomic snapshots that guarantee data consistency.

Yet this integration has never been without friction. The recent phase was marked by highly publicized disagreements between lead developer Kent Overstreet and Linus Torvalds over the management of feature additions directly in Linux kernel candidate branches. This situation led to a strong decision: the immediate standby of BCacheFS development in the official kernel starting with Linux 6.17. The official objective is clear:

to guarantee the quality and stability of the Linux kernel by avoiding the integration of features that are immature or pose significant risks to user data. Major Linux distributions quickly responded to this decision. For example, SuSE announced the deactivation of BCacheFS starting with kernel 6.17, forcing affected users to install the DKMS module manually. Some distributions, such as Arch Linux, are considering integrating this DKMS module directly into their official repositories, thus easing the transition for users, but without switching to full kernel integration. This removal raises several questions about the flexibility of the Linux kernel module integration model. BCacheFS, which relies on innovations in core storage, perfectly illustrates the challenges posed by rapid developments in open source when maintainers and contributors do not share the same roadmap.The challenges of file system stability and security in the Linux kernel.

The responsibility of Linux maintainers in controlling the addition of new features.

The DKMS model as an alternative for external integration, allowing for faster development while avoiding impacts on the main kernel.

  • To understand the issues in more detail, it is useful to consult the in-depth technical analysis on LinuxEncaja:
  • Developer Disagreements and Impact on BCacheFS
  • .

Learn how to install and configure bcachefs with dkms on Linux to benefit from a powerful and flexible file system, adapted to the needs of servers and advanced users. The Evolution to the DKMS Module: Operation, Benefits, and Constraints for BCacheFSThe choice to distribute BCacheFS via DKMS marks a significant change in the way this file system will be delivered and maintained for Linux users. DKMS is a framework for automatically compiling and installing kernel modules—modules external to the main kernel—dynamically with each Linux kernel update.

Thanks to this approach, the BCacheFS module can follow its own development and patch cycle independently of official kernel updates. This provides flexibility in integrating new features or fixes without having to wait for strict validation from Linux maintainers or risking delays in the release of new kernel versions. However, this independence comes at a price:

Installation and management require more active user intervention:

Unlike kernel integration, the user must ensure that the DKMS module is correctly installed and recompiled during kernel updates.

Greater potential fragmentation:

The module must be compatible with each installed kernel version, and distributions must carefully manage this risk.

  • An increased risk of software conflicts: Non-kernel modules are less controlled, which can lead to more frequent incompatibilities or service interruptions.
  • In practice, installation of the BCacheFS module via DKMS is now integrated into Debian and Ubuntu distributions, thanks to the direct efforts of the BCacheFS maintainer. This support allows for simplified adoption on these very popular platforms, while also offering advanced users the ability to test functional advances without waiting for long Linux kernel cycles. For a more complete overview of the available DKMS packages and their installation, the dedicated page on Debian/Ubuntu provides detailed instructions for beginners and administrators:
  • Linux 6.17 RC4 and BCacheFS in DKMS .

Discover bcachefs dkms, a dynamic module for the Linux file manager bcachefs. Simplify the installation and update of bcachefs with dkms and improve the performance of your file system.

Key steps for installing and maintaining the DKMS module BCacheFS Installation of prerequisites: compilation tools, kernel headers, DKMS manager.Automatic download and compilation of the BCacheFS module with each kernel update.

Functionality tests with existing or new file systems.

Active monitoring of module and kernel updates.

  • Proactive resolution of potential conflicts with other modules or updates.
  • https://www.youtube.com/watch?v=lbXtul3JQ5I
  • Technical analysis of BCacheFS features and comparison with other Linux file systems
  • BCacheFS has established itself in the Linux file system landscape thanks to its innovative architecture, which combines a powerful Bcache-based cache with classic and advanced features of a modern system:
  • Copy-on-write (CoW) mechanism:
Guarantees data consistency without sacrificing performance.

Integrated encryption management:

Transparent cryptography for data security.

  • Transparent compression : storage optimization and volume reduction.
  • Atomic snapshots : secure and fast snapshot capabilities for recovery.
  • Significant scalability : suitable for infrastructures ranging from local servers to large clusters.
  • Compared to iconic file systems such as OpenZFS
  • or Btrfs, BCacheFS sought to combine their best features while addressing some persistent limitations. OpenZFS displays proven robustness for fault tolerance, while Btrfs integrates advanced features but is sometimes criticized for its stability in production. BCacheFS aimed to provide a compromise with:

increased performance thanks to its optimized cache; modern features such as native encryption and compression; a structured approach to minimize corruption risks.

Despite these advantages, the recent controversy and reported corruption issues have generated legitimate concerns, thus far hindering its widespread adoption in enterprises. These difficulties stemmed from both specific bugs and maintainers’ development methodologies. This situation is analyzed in detail on LinuxEncaja in an article discussing the complex future of BCacheFS and its position in the Linux ecosystem:

  • BCacheFS and its place in Linux 6.17
  • .
  • Discover how to install and use BCacheFS with DKMS to optimize the performance of your Linux file system. A complete guide, tips, and best practices.

Impact of BCacheFS’s evolution on Linux distributions and kernel module management The switch from BCacheFS to a DKMS module has practical implications for Linux distributions and their users. Distributions must now integrate this new model to provide a consistent user experience, especially for professionals and enthusiasts who rely on this innovative file system.Some key points to be aware of:

More complex dependency management

: Compatibility between the DKMS version of the module and the various kernel versions deployed by the distribution must be ensured.

Independent maintenance and updates

: BCacheFS maintainers can push patches at any time without waiting for Linux kernel cycles, but this requires increased vigilance.

  • Variable module distribution : Some distributions, such as Arch Linux, include the BCacheFS DKMS module by default, while others leave it up to users to install it themselves.
  • Stability risks : External integration theoretically increases the surface area of ​​incompatibilities, requiring rigorous testing.
  • Linux distributions will need to expand their system administration tools to integrate this dynamic specific to DKMS modules. This includes automated recompilation and proactive conflict management to ensure smooth use in enterprises and among home Linux enthusiasts. A notable case study is SuSE, which has already announced its intention to disable the kernel-integrated BCacheFS starting with Linux 6.17 and offer only the DKMS version. This decision maintains compatibility while aligning with the Linux kernel’s strict policy on quality and security:
  • Alternative kernels and future solutions .

Future outlook for BCacheFS and the maintenance of file modules in the Linux ecosystem The new organization around the DKMS module for BCacheFS raises broader questions about how file systems and other kernel modules are managed in the Linux world, a crucial issue for sustainability and innovation.First, this development highlights the essential role of Linux maintainers. They are responsible for the stability and consistency of the kernel, and must balance the ability to introduce new features with the necessary quality in production. The BCacheFS case illustrates a turning point in this discipline, potentially prompting a rethinking of module integration processes.

Second, DKMS offers a pragmatic solution that is highly valued in open source because it allows the development of kernel modules to be separated from that of the kernel itself. This promotes agile innovation, but requires rigorous organization among users and distributions to avoid conflicts.

Finally, the mosaic of community-led initiatives around distributions opens the way to a greater diversity of solutions. While some prefer a “pure” kernel with few external modules, others adopt a modular and adaptable strategy, where DKMS plays the role of technical conductor.

Better coordination between developers and maintainers is now essential.

The community needs to increase its skills to manage DKMS modules.

Linux distributions must expand their tools to facilitate the continuous integration of external modules.

The debates surrounding BCacheFS also highlight the clinical importance of ensuring the security and reliability of file systems in a context of exponential data growth and robustness requirements. This topic is a cross-cutting phenomenon across the entire Linux ecosystem, which can be explored in more depth on LinuxEncaja, particularly through articles such as:

  • The Future of Linux After Torvalds
  • or
  • Loss of Functionality in Linux

.