A NAS appliance built on bcachefs

github.com

5 points·khajdamowicz··4 comments

BcacheFS had so much promise. I followed development with a lot of interest for years. I was ecstatic when it was accepted into the official Linux kernel. And from there, it only went downhill.

This process was so sad to witness, especially because there was no good reason for any of this unraveling at all. It was 100% just a result of Kent’s inability to constructively work with others. There was a lot of interest and goodwill, and Linus was so patient for so long. There were no technical reasons for any of this. Kent is a great software engineer producing excellent output. Everybody tried to resolve the purely social issues… except for Kent.

Recently, Kent has gone completely off the rails, seemingly developing a serious AI psychosis. I hope he gets better, and I wish him all the best.

I'm using my filesystem since Dec 2024 and it's closer to 100TiB than 10TiB now. I once had an issue that was quickly solved by Kent and now it's stable for me.

Yes, I regret all that drama that I've witnessed. But I'm happy it's way past that now. Kernel can be developed in its pace and bcachefs develops in its own pace.

> Kernel can be developed in its pace and bcachefs develops in its own pace.

I agree. Upstreaming it in the first place was probably a mistake. In the end, it just caused a lot of stress for both sides.

Without upstreaming it wouldn't get traction it have now. I agree that things could be managed better to keep it in the upstream but without upstraming we would be in deeper woods than we are now and still a lot of more users is needed to get even more traction and make it even more bulletproof with real-world testing.

Reply on news.ycombinator.com