From: Joel Parthemore <joel@parthemores.com>
To: Yu Kuai <yukuai1@huaweicloud.com>, Roman Mamedov <rm@romanrm.net>
Cc: linux-raid@vger.kernel.org, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: request for help on IMSM-metadata RAID-5 array
Date: Mon, 25 Sep 2023 17:57:18 +0200 [thread overview]
Message-ID: <02a12a6d-eac4-51a1-e5ab-3df4d79bb87b@parthemores.com> (raw)
In-Reply-To: <4d606b3d-ccec-e791-97ba-2cb5af0cc226@huaweicloud.com>
Den 2023-09-25 kl. 03:43, skrev Yu Kuai:
> Hi,
>
> 在 2023/09/24 2:49, Joel Parthemore 写道:
>> So, dd finally sped up and finished. It appears that I have lost none
>> of my data. I am a very happy man. A question: is there anything
>> useful I am likely to discover from keeping the RAID array as it is a
>> bit longer before I recreate it and copy the data back?
>
> It'll be much helper for developers to collect kernel stack for all
> stuck thread(and it'll be much better to use add2line).
Presuming I can re-create the problem, let me know what I should do to
collect that information for you. I'm very much a newbie in that area.
Joel
next prev parent reply other threads:[~2023-09-25 15:57 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
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 [this message]
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=02a12a6d-eac4-51a1-e5ab-3df4d79bb87b@parthemores.com \
--to=joel@parthemores.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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