> Once the BCacheFS maintainer behaves and the code is maintained upstream again, we will re-enable... (As IMO, it is a useful feature.)
How cynical. It's the kernel maintainer, not the bcachefs maintainer, who does not behave and has a huge history of unprofessional behavior for decades.
qalmakka · 24m ago
RIP BCacheFS. I was hopeful I could finally have a modern filesystem in Linux mainlined (I don't trust Btrfs anymore), but I guess I'll keep on having to install ZFS for the foreseeable future I guess.
As I predicted, out of tree bcachefs is basically dead on arrival - everybody interested is already on ZFS, btrfs is still around only because ZFS can't be mainlined basically
sureglymop · 5m ago
I've never had any issues with either ZFS or Btrfs after 2020. I wonder what you all are doing to have such issues with them.
Ygg2 · 17m ago
Wait. You don't trust Btrfs but you would trust BCacheFS, that's obviously very experimental?
rurban · 7m ago
Still more stable than btrfs. btrfs is also dead slow
kiney · 7m ago
btrfs has many technical advantages over zfs
debazel · 4m ago
Yes, like destroying itself and losing all data.
the_duke · 15m ago
This is a tragedy, bcachefs has so many great features...
motorest · 45m ago
Ultimately that's the right call, and the inevitable one as well.
lupusreal · 45m ago
The way the BCacheFS situation has been playing out is a tragedy. I had very high hopes for it.
johnisgood · 8m ago
Same. I liked many of its features (actually, all features, see https://bcachefs.org) and I was waiting for it to become usable, but I guess that day will never come now?
So, the alternative is ZFS only, maybe HAMMER2. HAMMER2 does not look too bad either, except you need DragonflyBSD for that.
InsideOutSanta · 10m ago
Yeah, this all seems so unnecessary. I hope Kent can either figure out how to work in the context of a larger team or find somebody who can do it on his behalf.
johnisgood · 6m ago
> Once the BCacheFS maintainer behaves [...]
So, there are still behavioral issues here I take it? That is a bummer. This is not news to me, but I thought the situation has changed ever since.
bgwalter · 51m ago
[deleted wrongthink]
hebocon · 42m ago
"behave" in this context can refer to simply respecting existing norms about RC code freezing.
graemep · 45m ago
There is an apology for that comment and a rewording further down the thread. Evidently made by someone who is not a native speaker who did not realise how it comes across.
teekert · 38m ago
Good addition,thanx.
I've been in a similar situation, letting everyone know I was fired. Apparently in the US this has a negative connotation, and they use "being let go" (or something confusing as "handing in/being handed your 2 weeks notice", a concept completely unknown here). Here we only have one word for "your company terminating your employment", and there is no negative connotation associated with it. This can be difficult for non-natives. We can come across very weird or less intelligent.
How cynical. It's the kernel maintainer, not the bcachefs maintainer, who does not behave and has a huge history of unprofessional behavior for decades.
As I predicted, out of tree bcachefs is basically dead on arrival - everybody interested is already on ZFS, btrfs is still around only because ZFS can't be mainlined basically
So, the alternative is ZFS only, maybe HAMMER2. HAMMER2 does not look too bad either, except you need DragonflyBSD for that.
So, there are still behavioral issues here I take it? That is a bummer. This is not news to me, but I thought the situation has changed ever since.
I've been in a similar situation, letting everyone know I was fired. Apparently in the US this has a negative connotation, and they use "being let go" (or something confusing as "handing in/being handed your 2 weeks notice", a concept completely unknown here). Here we only have one word for "your company terminating your employment", and there is no negative connotation associated with it. This can be difficult for non-natives. We can come across very weird or less intelligent.