From: Bob Brand <brand@wmawater.com.au>
To: "Reindl Harald" <h.reindl@thelounge.net>,
"Roger Heflin" <rogerheflin@gmail.com>,
"Wols Lists" <antlists@youngman.org.uk>
Cc: "Linux RAID" <linux-raid@vger.kernel.org>,
"Phil Turmel" <philip@turmel.org>, "NeilBrown" <neilb@suse.com>
Subject: RE: Failed adadm RAID array after aborted Grown operation
Date: Fri, 13 May 2022 15:32:36 +1000 (AEST) [thread overview]
Message-ID: <00b801d8668a$da017c00$8e047400$@wmawater.com.au> (raw)
In-Reply-To: <b2a3c4ec-2f86-7775-c84f-2f360ab9cfd0@thelounge.net>
This may not be the forum to ask this but what exactly is "compiling the
kernel". From what I've been reading, it sounds like a somewhat involved and
complex process - is it? Is compiling a new kernel the same as upgrading the
OS? I'm getting the impression that it sort of is but sort of isn't. Is it
possible to compile a kernel for a rescue CD (from the comments I've read,
it is possible)? If I were to compile a new kernel, would I expect the
version number for the kernel and mdadm to be the same? Sorry for all the
question but, as I said at the outset, a lot of this is all very new to me.
Thank you,
Bob
-----Original Message-----
From: Reindl Harald <h.reindl@thelounge.net>
Sent: Thursday, 12 May 2022 12:59 AM
To: Bob Brand <brand@wmawater.com.au>; Roger Heflin <rogerheflin@gmail.com>;
Wols Lists <antlists@youngman.org.uk>
Cc: Linux RAID <linux-raid@vger.kernel.org>; Phil Turmel
<philip@turmel.org>; NeilBrown <neilb@suse.com>
Subject: Re: Failed adadm RAID array after aborted Grown operation
Am 11.05.22 um 16:56 schrieb Reindl Harald:
>
>
> Am 11.05.22 um 15:22 schrieb Bob Brand:
>> Sorry Reindl. I'm not sure I understand. Are you saying I did or
>> didn't do the right thing in booting from a CentOS rescue disk? At
>> the moment it's running from the rescue disk and, be it the best
>> distro to have used (or not), I would imagine that I need to keep
>> running from the rescue disk until the reshape is complete as
>> rebooting in the middle of a reshape is what got me in this mess.
and nowhere did i say reboot now
and i only responded to your "Do I understand that you would recommend
upgrading our installation of Linux once the repair is complete or are
advising downloading and compiling a new kernel as part of the repair?"
nobody said that - the only point was use a as recent kernel as possible
with all rgow/reshape operations
> and i don't understand what you did not understand in the clear
> response below you got days ago!
>
> due reshape you where advised use whatever rescue/live system with a
> recent kernel and mdadm, not more and not less
>
> just to avoid probaly long fixed bugs in your old kernel
>
> ---------------------
>
> Try and get a CentOS 8.5 disk. At the end of the day, the version of
> linux doesn't matter. What you need is an up-to-date rescue disk.
> Distro/whatever is unimportant - what IS important is that you are
> using the latest mdadm, and a kernel that matches.
>
> The problem you have sounds like a long-standing but now-fixed bug. An
> original CentOS disk might be okay (with matched kernel and mdadm),
> but almost certainly has what I consider to be a "dodgy" version of mdadm.
>
> If you can afford the downtime, after you've reverted the reshape, I'd
> try starting it again with the rescue disk. It'll probably run fine.
> Let it complete and then your old CentOS 7 will be fine with it
CAUTION!!! This E-mail originated from outside of WMA Water. Do not click
links or open attachments unless you recognize the sender and know the
content is safe.
next prev parent reply other threads:[~2022-05-13 5:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 13:18 Failed adadm RAID array after aborted Grown operation Bob Brand
2022-05-08 15:32 ` Wols Lists
2022-05-08 22:04 ` Bob Brand
2022-05-08 22:15 ` Wol
2022-05-08 22:19 ` Bob Brand
2022-05-08 23:02 ` Bob Brand
2022-05-08 23:32 ` Bob Brand
2022-05-09 0:09 ` Bob Brand
2022-05-09 6:52 ` Wols Lists
2022-05-09 13:07 ` Bob Brand
[not found] ` <CAAMCDecTb69YY+jGzq9HVqx4xZmdVGiRa54BD55Amcz5yaZo1Q@mail.gmail.com>
2022-05-11 5:39 ` Bob Brand
2022-05-11 12:35 ` Reindl Harald
2022-05-11 13:22 ` Bob Brand
2022-05-11 14:56 ` Reindl Harald
2022-05-11 14:59 ` Reindl Harald
2022-05-13 5:32 ` Bob Brand [this message]
2022-05-13 8:18 ` Reindl Harald
2022-05-20 15:13 ` Bob Brand
2022-05-20 15:41 ` Reindl Harald
2022-05-22 4:13 ` Bob Brand
2022-05-22 11:25 ` Reindl Harald
2022-05-22 13:31 ` Wols Lists
2022-05-22 22:54 ` Bob Brand
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='00b801d8668a$da017c00$8e047400$@wmawater.com.au' \
--to=brand@wmawater.com.au \
--cc=antlists@youngman.org.uk \
--cc=h.reindl@thelounge.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=philip@turmel.org \
--cc=rogerheflin@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