[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240830072721.2112006-1-yukuai1@huaweicloud.com>
Date: Fri, 30 Aug 2024 15:27:14 +0800
From: Yu Kuai <yukuai1@...weicloud.com>
To: mariusz.tkaczyk@...el.com,
song@...nel.org
Cc: linux-raid@...r.kernel.org,
linux-kernel@...r.kernel.org,
yukuai3@...wei.com,
yukuai1@...weicloud.com,
yi.zhang@...wei.com,
yangerkun@...wei.com
Subject: [PATCH md-6.12 0/7] md: enhance faulty chekcing for blocked handling
From: Yu Kuai <yukuai3@...wei.com>
The lifetime of badblocks:
- IO error, and decide to record badblocks, and record sb_flags;
- write IO found rdev has badblocks and not yet acknowledged, then this
IO is blocked;
- daemon found sb_flags is set, update superblock and flush badblocks;
- write IO continue;
Main idea is that badblocks will be set in memory fist, before badblocks
are acknowledged, new write request must be blocked to prevent reading
old data after power failure, and this behaviour is not necessary if rdev
is faulty in the first place.
Yu Kuai (7):
md: add a new helper rdev_blocked()
md: don't wait faulty rdev in md_wait_for_blocked_rdev()
md: don't record new badblocks for faulty rdev
md/raid1: factor out helper to handle blocked rdev from
raid1_write_request()
md/raid1: don't wait for Faulty rdev in wait_blocked_rdev()
md/raid10: don't wait for Faulty rdev in wait_blocked_rdev()
md/raid5: don't set Faulty rdev for blocked_rdev
drivers/md/md.c | 8 +++--
drivers/md/md.h | 24 +++++++++++++++
drivers/md/raid1.c | 75 +++++++++++++++++++++++----------------------
drivers/md/raid10.c | 40 +++++++++++-------------
drivers/md/raid5.c | 13 ++++----
5 files changed, 92 insertions(+), 68 deletions(-)
--
2.39.2
Powered by blists - more mailing lists