fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

11K
active users

#bcachefs

0 posts0 participants0 posts today

The idea of #meritocracy only works if everyone is completely sure about the goals - like with #Linux and the #LinuxFoundation.

It's about machine code, low level programming and serving drivers for hardware enablement. You can pretty much quantify meritocratic value by quality of contribution - even in terms of #CoC, as we can see with #BcacheFS.

But, in #politics? There's no such thing. This is proven with finality by #Trump, as he calls it meritocratic, but hires ill-fitting candidates.

This morning, I came across this interesting article in the fantastic @vermaden newsletter:

Migrating away from bcachefs - blog.sesse.net/blog/tech/2025-

bcachefs is a filesystem with some intriguing features. The problem with all filesystems is that they are hard to implement, challenging to debug, and, worst of all, the most critical part of a system. Stability is undoubtedly important - a crash causing a reboot is manageable - but a filesystem that eats data is something irreparable or, at the very least, extremely dangerous.
Sure, there are backups (because there are backups, right?). But in my opinion, a backup is a last resort, not a solution.

Sometimes people ask me why I prefer ZFS over btrfs, especially when the latter is "more flexible." There are various reasons, but primarily, it’s due to the stability ZFS has shown me over many years of use. I've never lost data with ZFS, while I have lost data (non-critical, recoverable) several times with btrfs.

bcachefs is interesting - but before I consider it stable and usable, many, many years will have to pass.

blog.sesse.netSteinar H. Gunderson
#zfs#openzfs#btrfs

Migrating away from

blog.sesse.net/blog/tech/2025-

Steinar H. Gunderson aka Sesse writes:

'"[…] I've converted my last bcachefs filesystem to XFS, and I don't intend to look at it again in the near future. […]

I no longer trust bcachefs' future. […]

[…] I've had catastrophic data loss bugs that went unfixed for weeks despite multiple people reporting them. I've seen strange read performance issues. I've had oopses. […] “oh, yeah, that's a known issue […]

There are more things: […]"'

A few bits from the main merge for 6.14:

git.kernel.org/torvalds/c/2622

"'Lots of scalability work, another big on-disk format change. […]

Like 6.11, this is another big and xpensive automatic/required on disk format upgrade. This is planned to be the last big on disk format upgrade before the experimental label comes off. There will be one more minor on disk format update for a few things that couldn't make this release.'"

git.kernel.orgMerge tag 'bcachefs-2025-01-20.2' of git://evilpiepirate.org/bcachefs - kernel/git/torvalds/linux.git - Linux kernel source tree

With the status of bcachefs being what it is, is it time to switch back to zfs? What are your opinions? I don't have a lot of data on my bcachefs disk, because I was uncertain, and I feel I was right to, but it also makes it easy to switch back.

Continued thread

3/ There is now a official msg from the Foundation Technical Advisory Board (TAB) to developer Kent Overstreet based on a recommendation from the Code of Conduct Committee :

lore.kernel.org/all/6740fc3aab

'"[…] written abuse of another community member required action on your part to repair the damage to the individual and the community. You took insufficient action[…]

- Restrict participation in the kernel development process during the Linux 6.13 kernel […]"'

Replied in thread

@opennet неизбежное случилось, всё то, к чему вели новости о #bcachefs. Судя по моим познаниям фс крутая, но некоторые действия разрабов приводят к таким последствиям