From: Roman Mamedov <rm@romanrm.net>
To: Joel Parthemore <joel@parthemores.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: request for help on IMSM-metadata RAID-5 array
Date: Sat, 23 Sep 2023 16:24:49 +0500 [thread overview]
Message-ID: <20230923162449.3ea0d586@nvm> (raw)
In-Reply-To: <507b6ab0-fd8f-d770-ba82-28def5f53d25@parthemores.com>
On Sat, 23 Sep 2023 12:54:52 +0200
Joel Parthemore <joel@parthemores.com> wrote:
> the RAID array looking seemingly okay (according to mdadm -D) BUT this
> time, any attempt to access the RAID array or even just stop the array
> (mdadm --stop /dev/md126, mdadm --stop /dev/md127) once it was started
> would cause the RAID array to lock up. That means (I think) that I can't
> create an image of the array contents using dd, which is what -- of
> course -- I should have done in the first place. (I could assemble the
> RAID array read-only, but the RAID array is out of sync because it
> didn't shut down properly.)
Does accessing the array also lock up when it's assembled read-only?
The out-of-sync should not be a great issue, because only a tiny portion that
was being written at the time of crash would be out of sync. The rest should be
fine, and you could try backing up your important data.
If #1 is yes, then try a different distro with a newer kernel version.
--
With respect,
Roman
next prev parent reply other threads:[~2023-09-23 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 10:54 request for help on IMSM-metadata RAID-5 array Joel Parthemore
2023-09-23 11:24 ` Roman Mamedov [this message]
2023-09-23 15:18 ` Joel Parthemore
2023-09-23 15:35 ` Roman Mamedov
2023-09-23 15:45 ` Joel Parthemore
2023-09-23 18:49 ` Joel Parthemore
2023-09-25 1:43 ` Yu Kuai
2023-09-25 15:57 ` Joel Parthemore
2023-09-26 1:10 ` Yu Kuai
2023-09-29 19:44 ` Joel Parthemore
[not found] ` <a0b8a693-5d9c-d354-5afc-4500b78a983e@huaweicloud.com>
2023-10-05 7:28 ` Joel Parthemore
2023-09-25 9:44 ` Mariusz Tkaczyk
2023-09-25 15:52 ` Joel Parthemore
2023-09-25 16:43 ` Mariusz Tkaczyk
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=20230923162449.3ea0d586@nvm \
--to=rm@romanrm.net \
--cc=joel@parthemores.com \
--cc=linux-raid@vger.kernel.org \
/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