From: Doug V Johnson <dougvj@dougvj.net>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Doug Johnson <dougvj@gmail.com>, Song Liu <song@kernel.org>,
"open list:SOFTWARE RAID (Multiple Disks) SUPPORT"
<linux-raid@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH 1/2] md/raid5: skip stripes with bad reads during reshape to avoid stall
Date: Mon, 27 Jan 2025 08:51:26 +0000 [thread overview]
Message-ID: <25cd636a52da0db2db91a220a9eea68b@dougvj.net> (raw)
In-Reply-To: <9c3420a9-8f6a-1102-37d2-8f32787b2f9a@huaweicloud.com>
> So, perhaps just abort the reshape will make more sense to me, because
> user will lost more data if so.
Ah yes, I agree that does make more sense. I appreciate the prompt
feedback and explanation. I will submit a v2 soon.
next prev parent reply other threads:[~2025-01-27 8:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 1:26 Doug V Johnson
2025-01-25 1:26 ` [PATCH 2/2] md/raid5: warn when failing a read due to bad blocks metadata Doug V Johnson
2025-01-26 6:27 ` [PATCH 1/2] md/raid5: skip stripes with bad reads during reshape to avoid stall Yu Kuai
2025-01-27 8:51 ` Doug V Johnson [this message]
2025-01-27 9:00 ` [PATCH v2 1/2] md/raid5: freeze reshape when encountering a bad read Doug V Johnson
2025-01-27 9:00 ` [PATCH v2 2/2] md/raid5: warn when failing a read due to bad blocks metadata Doug V Johnson
2025-02-08 2:49 ` [PATCH v2 1/2] md/raid5: freeze reshape when encountering a bad read Yu Kuai
2025-02-18 7:20 ` Doug V Johnson
2025-02-24 9:02 ` [PATCH v3 1/3] " Doug V Johnson
2025-02-24 9:02 ` [PATCH v3 2/3] md/raid5: warn when failing a read due to bad blocks metadata Doug V Johnson
2025-02-24 9:02 ` [PATCH v3 3/3] md/raid5: check for overlapping bad blocks before starting reshape Doug V Johnson
2025-03-05 6:36 ` Yu Kuai
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=25cd636a52da0db2db91a220a9eea68b@dougvj.net \
--to=dougvj@dougvj.net \
--cc=dougvj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--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
all inboxes | Powered by JetHome®