From: Yunye Zhao <yunye.zhao@linux.alibaba.com>
To: Song Liu <song@kernel.org>, Yu Kuai <yukuai@fygo.io>
Cc: Li Nan <magiclinan@didiglobal.com>, Xiao Ni <xiao@kernel.org>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Yunye Zhao <yunye.zhao@linux.alibaba.com>
Subject: [PATCH v2 3/3] md/raid10: skip clean regions in bulk during recovery
Date: Thu, 23 Jul 2026 21:55:35 +0800 [thread overview]
Message-ID: <20260723135535.101995-4-yunye.zhao@linux.alibaba.com> (raw)
In-Reply-To: <20260723135535.101995-1-yunye.zhao@linux.alibaba.com>
During recovery of a degraded RAID10 with a mostly-clean bitmap, the
"everything skipped" path (biolist == NULL) returns max_sync == 128
sectors, even though md_bitmap_start_sync() already reported a much
larger clean range (an unallocated bitmap page spans 2^31 sectors with
a 512M bitmap chunk). On the reported 2^40-sector array md_do_sync()
then crawls through 2^33 no-op iterations, burning a CPU for the whole
sweep; the cond_resched() in md_do_sync()'s skip path only stops the
watchdog firing.
The skip path cannot simply return sync_blocks: sync_blocks is measured
in array sectors while the return value advances the per-device recovery
cursor, and the two spaces differ by the raid10 layout. For a near
layout (far_copies == 1 && !far_offset) the mapping is linear with slope
raid_disks / near_copies; when near_copies evenly divides raid_disks the
conversion is exact. Track the minimum clean span across the skipped
devices, convert it to device sectors and skip it in one step.
far/offset layouts are not a linear scale and keep the previous
behaviour.
Only devices skipped as clean feed that minimum, and the skip is
suppressed when a device needed rebuilding but had no readable source
(missing_source), so the cursor never jumps past sectors that still
need recovery.
The generic bitmap skip_sync_blocks() path cannot be used here: it does
not see mrdev/mreplace (the recovery target and its replacement), and
replacement targets must rebuild even bitmap-clean chunks.
On a mostly-clean array with 8T per device (near=2, 4 disks) the
recovery sweep drops from 37.2s of CPU spinning to about 10ms.
Signed-off-by: Yunye Zhao <yunye.zhao@linux.alibaba.com>
---
drivers/md/raid10.c | 46 ++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 43 insertions(+), 3 deletions(-)
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
index 54cddb3a98cd..8acbd5ef618b 100644
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -3176,6 +3176,9 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr,
int i;
int max_sync;
sector_t sync_blocks;
+ sector_t min_sync_blocks = MaxSector;
+ sector_t sync_end;
+ bool missing_source = false;
sector_t chunk_mask = conf->geo.chunk_mask;
int page_idx = 0;
@@ -3258,6 +3261,14 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr,
if (max_sector > mddev->resync_max)
max_sector = mddev->resync_max; /* Don't do IO beyond here */
+ /*
+ * The chunk clamp below caps a single sync I/O to at most one chunk.
+ * The bitmap-clean recovery skip issues no I/O, so remember the real
+ * end here to bound the skip against it rather than the chunk
+ * boundary.
+ */
+ sync_end = max_sector;
+
/* make sure whole request will fit in a chunk - if chunks
* are meaningful
*/
@@ -3334,9 +3345,13 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr,
if (!must_sync &&
mreplace == NULL &&
!conf->fullsync) {
- /* yep, skip the sync_blocks here, but don't assume
- * that there will never be anything to do here
+ /* Skip the clean sync_blocks here; don't
+ * assume there will never be anything to
+ * do. Only a genuinely skipped clean span
+ * may widen the bulk skip below.
*/
+ if (sync_blocks < min_sync_blocks)
+ min_sync_blocks = sync_blocks;
continue;
}
if (mrdev)
@@ -3459,6 +3474,7 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr,
if (j == conf->copies) {
/* Cannot recover, so abort the recovery or
* record a bad block */
+ missing_source = true;
if (any_working) {
/* problem is that there are bad blocks
* on other device(s)
@@ -3514,6 +3530,8 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr,
}
}
if (biolist == NULL) {
+ sector_t skip_sectors = max_sync;
+
while (r10_bio) {
struct r10bio *rb2 = r10_bio;
r10_bio = (struct r10bio*) rb2->master_bio;
@@ -3521,7 +3539,29 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr,
put_buf(rb2);
}
*skipped = 1;
- return max_sync;
+
+ /*
+ * min_sync_blocks is in array sectors, but the return
+ * value advances the per-device cursor; for a near
+ * layout the two spaces differ by the factor
+ * raid_disks / near_copies.
+ */
+ if (!missing_source &&
+ conf->geo.far_copies == 1 && !conf->geo.far_offset &&
+ conf->geo.raid_disks % conf->geo.near_copies == 0 &&
+ min_sync_blocks != MaxSector) {
+ sector_t clean_sectors = min_sync_blocks;
+
+ clean_sectors *= conf->geo.near_copies;
+ sector_div(clean_sectors, conf->geo.raid_disks);
+ clean_sectors &= ~chunk_mask;
+ if (clean_sectors > sync_end - sector_nr)
+ clean_sectors = sync_end - sector_nr;
+ if (clean_sectors > skip_sectors)
+ skip_sectors = clean_sectors;
+ }
+
+ return skip_sectors;
}
} else {
/* resync. Schedule a read for every block at this virt offset */
--
2.19.1.6.gb485710b
next prev parent reply other threads:[~2026-07-23 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 6:27 [PATCH] md: fix soft lockup during resync when sync is repeatedly skipped Yunye Zhao
2026-07-17 6:51 ` sashiko-bot
2026-07-19 10:45 ` yu kuai
2026-07-20 6:20 ` Yunye Zhao
2026-07-22 4:00 ` yu kuai
2026-07-23 13:55 ` [PATCH v2 0/3] md/raid10: fix recovery corruption and soft lockup on large arrays Yunye Zhao
2026-07-23 13:55 ` [PATCH v2 1/3] md/raid10: fix still_degraded being inverted in raid10_sync_request() Yunye Zhao
2026-07-23 13:55 ` [PATCH v2 2/3] md: add cond_resched() to md_do_sync()'s skip path Yunye Zhao
2026-07-23 14:05 ` sashiko-bot
2026-07-23 13:55 ` Yunye Zhao [this message]
2026-07-23 14:16 ` [PATCH v2 3/3] md/raid10: skip clean regions in bulk during recovery sashiko-bot
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=20260723135535.101995-4-yunye.zhao@linux.alibaba.com \
--to=yunye.zhao@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=magiclinan@didiglobal.com \
--cc=song@kernel.org \
--cc=xiao@kernel.org \
--cc=yukuai@fygo.io \
/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