From: antlists <antlists@youngman.org.uk>
To: John Stoffel <john@stoffel.org>
Cc: Thomas Grawert <thomasgrawert0282@gmail.com>,
linux-raid@vger.kernel.org, Phil Turmel <philip@turmel.org>
Subject: Re: help requested for mdadm grow error
Date: Mon, 25 May 2020 22:55:12 +0100 [thread overview]
Message-ID: <a9576863-cfce-1c08-078b-ca945bb8b551@youngman.org.uk> (raw)
In-Reply-To: <24268.15511.752645.491837@quad.stoffel.home>
On 25/05/2020 22:45, John Stoffel wrote:
> This is Debian Buster, and it's he's upto date with debian packages,
> he's almost certainly in a stable setup. Now maybe we need to talk
> with the Debian package maintainer for mdadm and ask them to upgrade,
> or maybe why they haven't updated recently.
If you're going to do that, I think you need to get the kernel
maintainer to upgrade that as well...
As I see it, the CAUSE of the problem is that we have an old-but-updated
frankenkernel. It doesn't matter whether mdadm is contemporary with the
original pre-franken-state kernel or contemporary with the new
up-to-date frankenkernel, the fact of the matter is that the
relationship between mdadm and the kernel isn't regression tested beyond
making sure that arrays assemble and run correctly.
Hence the inevitable screw-ups when users try to administer their arrays.
Cheers,
Wol
next prev parent reply other threads:[~2020-05-25 21:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 17:25 help requested for mdadm grow error Thomas Grawert
2020-05-25 18:09 ` Wols Lists
2020-05-25 18:18 ` Thomas Grawert
2020-05-25 18:55 ` Wols Lists
2020-05-25 19:05 ` Thomas Grawert
2020-05-25 19:20 ` Wols Lists
2020-05-25 21:45 ` John Stoffel
2020-05-25 21:55 ` antlists [this message]
2020-05-25 19:33 ` Mikael Abrahamsson
2020-05-25 19:35 ` Thomas Grawert
2020-05-25 19:42 ` Andy Smith
2020-05-25 20:30 ` Thomas Grawert
2020-05-25 21:19 ` antlists
2020-05-25 21:22 ` Thomas Grawert
2020-05-25 22:02 ` antlists
2020-05-25 22:18 ` Thomas Grawert
2020-05-25 22:32 ` antlists
2020-05-25 23:01 ` Thomas Grawert
2020-05-25 23:15 ` Thomas Grawert
2020-05-25 23:31 ` Thomas Grawert
2020-05-26 1:16 ` antlists
2020-05-26 1:16 ` Thomas Grawert
2020-05-25 18:24 ` Thomas Grawert
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=a9576863-cfce-1c08-078b-ca945bb8b551@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=thomasgrawert0282@gmail.com \
/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