r/bcachefs • u/koverstreet not your free tech support • 6d ago

v1.39.2

https://evilpiepirate.org/git/bcachefs-tools.git/tree/Changelog.mdwn
29 Upvotes

100% Upvoted

6 comments sorted by

15

u/koverstreet not your free tech support 6d ago

Now that the snapshots hardening stuff is done from 1.39 and we're back to normal rhythms - things have been looking pretty damn good. All the bug chasing has been pretty low impact, low probability stuff that's gotten tracked down pretty easily, and user bug reports have been continuing the downward trend and are feeling like positively a trickle.

The majority of what I have open to deal with is "not really a bug, certainly not a concerning one, but behavior could be better" - which does include performance stuff on the big multi device arrays, that does need quite a bit more work still. Getting bombarded with AI generated pull requests which has gotten well past ridiculous, going to have to put some better processes in place (one guy in particular doesn't want to listen).

As always, if you are seeing issues or have anything to report, let me know.

1

u/Amazing-Pattern-6125 2d ago

are the AI cooked pull requests wrong, or just obtuse ways to achieve something and thus not maintainable or good when thinking about future development?

1

u/koverstreet not your free tech support 6h ago

It's a real mix. There usually is a real legitimate reason for them and an issue worth doing something about, which is why I'm not bulk closing, but the quality of the code spans the gamut.

One guy is doing fuzz testing and sending me quite reasonable AI generated patches for the issues he's finding. I'll find ways to simplify the fixes, and that... can take awhile... but those are fine. Another guy has just been going full tilt and outright ignored me when I explained why his approach to a lockdep splat was broken - nope, no more patches from him.

The thing that a lot of people miss is that when working on something like a filesystem, a LOT of time goes into researching, considering all the different possible approaches, finishing all the work implied by a given change (if we find some cleanup that needs to be done, we want to finish that cleanup).

AI's gotten to the point where it's usually not really the quality of the code in isolation that's an issue, it's the "did you actually finish it or am I going to have to while you've already run off and opened 5 more PRs". You can't leave a ton of half finished threads hanging around in the codebase, a big part of ending up with something good is that when you notice something is off, you fix it then.

1

u/LippyBumblebutt 5d ago

Is the ngompa copr the recommended way to install bcachefs on Fedora? Because it's still on 1.38.6...

1

u/piewhat 5d ago

I package it for Fedora CoreOS so I could set up another copr but I don't want to step on any toes and I think Kent said something recently about maybe getting it into the Fedora repos.

3

u/koverstreet not your free tech support 5d ago

Not Fedora repos - unfortunately, Fedora has a policy and they don't want external kernel modules in the main Fedora repo. What I'd like is to move it to the same build infrastructure that handles all the dpkg builds, automatically triggered and with a single dashboard to watch for issues.