An inspirational reply of koverstreet https://lwn.net/Articles/1028572/ He is focused on solving all bug reports, and in iterating bcachefs in the faster way possible. It is a sort of implicit contract with its users base: “you are using bcachefs in production/real-world despite it is experimental, and I will support you restoring files and improving code”.
So, I can understand why he doesn’t like waiting too much before releasing improvements. The Linux kenernel release cycle can transform weeks in months if some bug-fixes requires new features or refactorings, like in case of a new file system. I’m sorry that him and Linux maintainers didn’t find a good approach.
BTW, I used bcachefs for 1-2 years with 3 HDD and 1 SSD in cache. It supported this usage scenario better than ZFS for a desktop/workstation like mine setting.
Pathetic 🤣
It’s like you’re a wannabe a troll, but you’re incapable of really hammering home the pendantic nature of facile incel ricochet insults.
Whenever you want to give up and admit you’re wrong, I’ll be here ignoring you.
Unfortunately, the troll here is the one who can’t be bothered to read people’s comment before replying. Try again.
An inspirational reply of koverstreet https://lwn.net/Articles/1028572/ He is focused on solving all bug reports, and in iterating bcachefs in the faster way possible. It is a sort of implicit contract with its users base: “you are using bcachefs in production/real-world despite it is experimental, and I will support you restoring files and improving code”.
So, I can understand why he doesn’t like waiting too much before releasing improvements. The Linux kenernel release cycle can transform weeks in months if some bug-fixes requires new features or refactorings, like in case of a new file system. I’m sorry that him and Linux maintainers didn’t find a good approach.
BTW, I used bcachefs for 1-2 years with 3 HDD and 1 SSD in cache. It supported this usage scenario better than ZFS for a desktop/workstation like mine setting.