From: Martin Steigerwald <martin@lichtvoll.de>
To: "Carl E. Thompson" <list-bcachefs@carlthompson.net>,
"Malte Schröder" <malte.schroeder@tnxip.de>
Cc: Christopher Snowhill <chris@kode54.net>,
"linux-bcachefs@vger.kernel.org" <linux-bcachefs@vger.kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: Re: Another bcachefs version downgrade bug
Date: Sat, 19 Oct 2024 10:31:25 +0200 [thread overview]
Message-ID: <4958287.GXAFRqVoOG@lichtvoll.de> (raw)
In-Reply-To: <1af6fd38-7ecf-451a-9be3-fa7b9447fa43@tnxip.de>
Hi Carl, hi Malte, hi,
Malte Schröder - 19.10.24, 10:13:08 MESZ:
> On 19/10/2024 02:15, Carl E. Thompson wrote:
> > If you tell me you don't want me testing bcachefs anymore it won't
> > hurt my feelings and I'll respect your wishes. There are plenty of
> > quality filesystems for me to use where I'll have less hassle. But
> > I'd suggest to you that pushing out testers who point out bugs and
> > try to offer constructive criticism isn't the best way to make
> > quality software.
>
> I think in your case the developer of the fs is the wrong person to
> complain to. The issues you are reporting have looong been fixed but
> apparently your distro neglected to provide these fixes to its users. So
> if you are stuck with a 6.9 series kernel, well, bcachefs was really
> not ready for daily use back then. 6.11 is fine, 6.12 seems to fix the
> last issue I was seeing. So I think the options you have are: get a
> newer kernel and/or choose a different fs.
While I certainly do not agree with Kent on everything – and also not with
the tone of some conversations –, I agree here about the basic situation:
BCacheFS is marked experimental. My take with that is: As long as it is
marked experimental and you like to test it and give feedback, it is
important to move quickly enough to new kernel versions. It was and partly
still is the same with BTRFS. Developers often asked users to use a newer
kernel. Feedback on BCacheFS on 6.9 is quite likely not very useful to
Kent and other BCacheFS developers while they already work on what to
bring in for 6.13.
It reminds me of an annoying issue with appointment reminders in KDE's
Plasma and one frustrated bug reporter expecting to fix the issue in the
version of the software it occured in. Due to the nature of the
implementation of restoring lost functionality the fix had some familiarity
with a new feature and was more than 100 lines changed in different files.
While I certainly get that it has been frustrating for the user, cause the
issue was annoying for me as well… I would not expect and basically demand
on how developers use their free time. Of course, Carl, in case you
support Kent financially regarding BCacheFS development… then that may be a
bit of a different story, but once kernels are out of stable support… I'd
still agree with Kent.
Best,
--
Martin
next prev parent reply other threads:[~2024-10-19 8:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 4:51 Another bcachefs version downgrade bug Carl E. Thompson
2024-10-17 0:09 ` Kent Overstreet
2024-10-17 8:29 ` Carl E. Thompson
2024-10-17 8:39 ` Kent Overstreet
2024-10-17 9:15 ` Carl E. Thompson
2024-10-17 9:30 ` Kent Overstreet
2024-10-17 9:45 ` Carl E. Thompson
2024-10-17 10:13 ` Kent Overstreet
2024-10-17 16:49 ` Carl E. Thompson
2024-10-18 8:17 ` Christopher Snowhill
2024-10-18 17:37 ` Carl E. Thompson
2024-10-18 19:12 ` Kent Overstreet
2024-10-19 0:15 ` Carl E. Thompson
2024-10-19 8:13 ` Malte Schröder
2024-10-19 8:31 ` Martin Steigerwald [this message]
2024-10-19 9:29 ` Carl E. Thompson
2024-10-20 9:29 ` Kent Overstreet
2024-10-19 20:18 ` Jani Partanen
2024-10-20 8:04 ` Malte Schröder
2024-10-21 3:49 ` Jani Partanen
2024-10-20 16:59 ` Kent Overstreet
2024-10-21 0:34 ` Carl E. Thompson
2024-10-21 1:15 ` Kent Overstreet
2024-10-21 7:43 ` Mounting multiple versions/snapshots/images at the same time (was: Re: Another bcachefs version downgrade bug) Martin Steigerwald
2024-10-21 20:15 ` Carl E. Thompson
2024-10-21 7:26 ` Another bcachefs version downgrade bug Martin Steigerwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4958287.GXAFRqVoOG@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=chris@kode54.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=list-bcachefs@carlthompson.net \
--cc=malte.schroeder@tnxip.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox