They seem to be dealing both with reliability and performance improvements since it's very much a work in progress. Making the current bcachefs iron clad right now is fairly pointless since the optimizations and performance improvements will change the state of the code, probably significantly. Make no mistake though they are focusing on bugs too. If you use it on a production system that's on you, and the sooner it is relevant in terms of performance the more people will use and report more bugs which then get fixed which gets more users etc. There are plenty of non-critical use-cases when you can throw in a not-necessarily-perfectly-stable filesystem if it has some feature that others don't have.
Nice to see great hygiene on this merge with no drama and hopefully this continues.
-
At this point the priority should not be performance. To build a good reputation, the main thing is to focus on reliability, something that Btrfs never achieved after more than a decade. A high score in a performance test is of no use if it is not backed up by bombproof endurance. The most important thing about a file system, for the average user, is to forget that it exists.
It doesn't matter if it is at turtle speed but please: DO NOT CORROMPT OR LOSE MY DATA.Leave a comment:
-
>"... and the developers being aware of areas for (performance) improvements moving ahead"
IMHO highest priority should be robustness and the possibility of Scrubbing with automatic repair.Leave a comment:
-
Bcachefs Lands Another Round Of Fixes For Linux 6.7
Phoronix: Bcachefs Lands Another Round Of Fixes For Linux 6.7
On Friday another round of fixes were merged for the Bcachefs file-system for the in-development Linux 6.7 kernel...
Leave a comment: