It was nowhere close to be mature enough to be in the kernel. The developer is nowhere close to be mature enough to be involved in the kernel. It’s better for everybody if it is developed separately and maybe integrated again at a later stage when the file system and tooling are considered stable and changes are smaller and less sensitive. CacheFS being in the kernel might mislead people to rely on a filesystem that is still experimental and under heavy development. Personally I am looking forward to see it mature because I’d love to run it on my file storage home server when it is stable enough.
That the developer himself finds it absolutely necessary to push new code outside the window for upcoming versions of the kernel is a pretty good indication.
That is a personality issue, not a code emergency.
There were two dozen patches submitted for 6.17 that were never merged. What has the fall-out been? Where are all the stories about data loss? I am sure they would hit the front page.
The file system can improve but it is already fine.
The fallout for people knowingly risking their data beta testing a filesystem that is still in experimental and some users running into issues and possibly corruption?
There are no stories because it is not a story when a test environment for finding bugs fails and the bugs get fixed. Nobody with data they can not lose are putting it on bcachefs because why would they.
Thanks for running a test environment though. Please take backups of anything important, just in case.
It was nowhere close to be mature enough to be in the kernel. The developer is nowhere close to be mature enough to be involved in the kernel. It’s better for everybody if it is developed separately and maybe integrated again at a later stage when the file system and tooling are considered stable and changes are smaller and less sensitive. CacheFS being in the kernel might mislead people to rely on a filesystem that is still experimental and under heavy development. Personally I am looking forward to see it mature because I’d love to run it on my file storage home server when it is stable enough.
I have been relying on the filesystem. It is excellent. It is mature enough.
Sadly, the lead dev for bcachefs is not mature enough.
what independently verifiable condition(s) will satisfy these requirements?
That the developer himself finds it absolutely necessary to push new code outside the window for upcoming versions of the kernel is a pretty good indication.
That is a personality issue, not a code emergency.
There were two dozen patches submitted for 6.17 that were never merged. What has the fall-out been? Where are all the stories about data loss? I am sure they would hit the front page.
The file system can improve but it is already fine.
The fallout for people knowingly risking their data beta testing a filesystem that is still in experimental and some users running into issues and possibly corruption?
There are no stories because it is not a story when a test environment for finding bugs fails and the bugs get fixed. Nobody with data they can not lose are putting it on bcachefs because why would they.
Thanks for running a test environment though. Please take backups of anything important, just in case.