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 · 15m 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.
jamesnorden · 9m ago
Ah yes, the famous "holding it wrong".
happymellon · 6m ago
I've also not had issues with BTRFS.
The question was around usage, because without knowing people's usecases and configurations it'll never be usable for you while working fine for others.
Ygg2 · 28m ago
Wait. You don't trust Btrfs but you would trust BCacheFS, that's obviously very experimental?
rurban · 17m ago
Still more stable than btrfs. btrfs is also dead slow
Iridiumkoivu · 1m ago
I agree with this sentiment.
Btrfs has destroyed itself on my testing/lab machines three times during last two years up to point where recovery wasn’t possible. Metadata corruption being main issue (or that how it looks like to me at least). As of now I trust BCacheFS way more and I’ve given it roughly the same time to prove itself as Btrfs. BCacheFS has issues but so far I’ve managed to resolve them without major data loss.
Note: I currently use ext4 in all ”really important” desktop/laptop installations and OpenZFS in my server. Performance being the main concern for desktop and reliability for server.
kiney · 17m ago
btrfs has many technical advantages over zfs
debazel · 14m ago
Yes, like destroying itself and losing all data.
natebc · 7m ago
ZFS is perfectly capable of this too.
source: worked as a support engineer for a block storage company, witnessed hundreds of customers blowing one or both of their feet off with ZFS.
crest · 3m ago
Can you give an example because to me it always appeared as NIH copy-cat fs?
rurban · 14m ago
> 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.
happymellon · 5m ago
The bcachefs maintainer has added new features during bugfix windows, and lied about it.
pantalaimon · 2m ago
It's still an experimental module, the feature was about gathering more debug information.
the_duke · 26m ago
This is a tragedy, bcachefs has so many great features...
motorest · 56m ago
Ultimately that's the right call, and the inevitable one as well.
lupusreal · 55m ago
The way the BCacheFS situation has been playing out is a tragedy. I had very high hopes for it.
InsideOutSanta · 20m 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 · 17m 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.
johnisgood · 19m 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.
bgwalter · 1h ago
[deleted wrongthink]
graemep · 56m 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.
dbdr · 4m ago
Funnily enough the apology ends with:
> If the above offended anyone, I sincerely apology them.
Unless this was tongue-in-cheek, this kind of proves the point that language was the cause. The apology is a good move in any case.
teekert · 48m 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.
T3OU-736 · 54s ago
In the US, the terminology tends to split into "fired" (implies "for valid reasons") vs "laid off" (implies "position was terminsted, this was not about the employee or their qualities and performance").
hebocon · 52m ago
"behave" in this context can refer to simply respecting existing norms about RC code freezing.
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
The question was around usage, because without knowing people's usecases and configurations it'll never be usable for you while working fine for others.
Btrfs has destroyed itself on my testing/lab machines three times during last two years up to point where recovery wasn’t possible. Metadata corruption being main issue (or that how it looks like to me at least). As of now I trust BCacheFS way more and I’ve given it roughly the same time to prove itself as Btrfs. BCacheFS has issues but so far I’ve managed to resolve them without major data loss.
Note: I currently use ext4 in all ”really important” desktop/laptop installations and OpenZFS in my server. Performance being the main concern for desktop and reliability for server.
source: worked as a support engineer for a block storage company, witnessed hundreds of customers blowing one or both of their feet off with ZFS.
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.
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.
So, the alternative is ZFS only, maybe HAMMER2. HAMMER2 does not look too bad either, except you need DragonflyBSD for that.
> If the above offended anyone, I sincerely apology them.
Unless this was tongue-in-cheek, this kind of proves the point that language was the cause. The apology is a good move in any case.
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.