The file system bcachefs is set to be removed from the main Linux kernel due to an ongoing conflict between its creator, Kent Overstreet, and key maintainers of the virtual memory subsystems (VM) and file systems (FS). Despite its technical advantages and active development, the project’s future has become uncertain.
bcachefs, which competes with BTRFS and ZFS as a Linux file system, utilizes the Copy-on-Write (COW) mechanism. This mechanism ensures that changes do not result in data rewriting. Instead, the new state is recorded in a new location with the pointer of the current state being updated. The removal of bcachefs from the main kernel tree will pose challenges for users who will now have to rely on third-party builds or wait for its official return to the main development branch.
The conflict between Kent and several key maintainers has been ongoing for years, with trust being a major issue. A recent disagreement regarding the Journal_rewind function further strained their relationship, prompting Linus Torvalds to emphasize the need for constructive collaboration to rebuild trust.
According to Linus, the trust issue is systemic and extends beyond personal relationships. He asserts that tangible evidence, not just promises of better behavior, is necessary to demonstrate effective collaboration with other developers. Linus maintains that this collaboration must occur while Bcachefs is maintained outside the main kernel tree.
Kent Overstreet contends that Bcachefs is stable and has a substantial user base. He affirms that he follows merge rules and only intervenes in critical situations. Kent advocates for a streamlined release process to promptly deliver fixes to users.
It appears that Bcachefs’ future lies in its development outside the main kernel codebase, through Linux distributions and third-party repositories. Reestablishing trust may take time and will require active involvement in other kernel projects and collaboration with respected maintainers.
This information was gathered from personal correspondence with Linus and Kent; thus, further details are not available at this time.