* [PATCH v4 0/2] md: fix sync_action show
@ 2025-08-16 0:25 Zheng Qixing
2025-08-16 0:25 ` [PATCH v4 1/2] md: add helper rdev_needs_recovery() Zheng Qixing
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Zheng Qixing @ 2025-08-16 0:25 UTC (permalink / raw)
To: song, yukuai3, linan122
Cc: linux-raid, linux-kernel, yi.zhang, yangerkun, houtao1,
zhengqixing, pmenzel
From: Zheng Qixing <zhengqixing@huawei.com>
Changes in v4:
Move "rdev->raid_disk >= 0" into rdev_needs_recovery().
Changes in v3:
Code style modification in patch 1.
Fix incorrect display of sync_action when raid is in resync.
Zheng Qixing (2):
md: add helper rdev_needs_recovery()
md: fix sync_action incorrect display during resync
drivers/md/md.c | 60 ++++++++++++++++++++++++++++++++++++++-----------
1 file changed, 47 insertions(+), 13 deletions(-)
--
2.39.2
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH v4 1/2] md: add helper rdev_needs_recovery()
2025-08-16 0:25 [PATCH v4 0/2] md: fix sync_action show Zheng Qixing
@ 2025-08-16 0:25 ` Zheng Qixing
2025-08-16 0:25 ` [PATCH v4 2/2] md: fix sync_action incorrect display during resync Zheng Qixing
2025-08-16 0:53 ` [PATCH v4 0/2] md: fix sync_action show Yu Kuai
2 siblings, 0 replies; 4+ messages in thread
From: Zheng Qixing @ 2025-08-16 0:25 UTC (permalink / raw)
To: song, yukuai3, linan122
Cc: linux-raid, linux-kernel, yi.zhang, yangerkun, houtao1,
zhengqixing, pmenzel
From: Zheng Qixing <zhengqixing@huawei.com>
Add a helper for checking if an rdev needs recovery.
Signed-off-by: Zheng Qixing <zhengqixing@huawei.com>
---
drivers/md/md.c | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index ac85ec73a409..3fcb061dd713 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -4835,6 +4835,15 @@ metadata_store(struct mddev *mddev, const char *buf, size_t len)
static struct md_sysfs_entry md_metadata =
__ATTR_PREALLOC(metadata_version, S_IRUGO|S_IWUSR, metadata_show, metadata_store);
+static bool rdev_needs_recovery(struct md_rdev *rdev, sector_t sectors)
+{
+ return rdev->raid_disk >= 0 &&
+ !test_bit(Journal, &rdev->flags) &&
+ !test_bit(Faulty, &rdev->flags) &&
+ !test_bit(In_sync, &rdev->flags) &&
+ rdev->recovery_offset < sectors;
+}
+
enum sync_action md_sync_action(struct mddev *mddev)
{
unsigned long recovery = mddev->recovery;
@@ -8968,11 +8977,7 @@ static sector_t md_sync_position(struct mddev *mddev, enum sync_action action)
start = MaxSector;
rcu_read_lock();
rdev_for_each_rcu(rdev, mddev)
- if (rdev->raid_disk >= 0 &&
- !test_bit(Journal, &rdev->flags) &&
- !test_bit(Faulty, &rdev->flags) &&
- !test_bit(In_sync, &rdev->flags) &&
- rdev->recovery_offset < start)
+ if (rdev_needs_recovery(rdev, start))
start = rdev->recovery_offset;
rcu_read_unlock();
@@ -9331,12 +9336,8 @@ void md_do_sync(struct md_thread *thread)
test_bit(MD_RECOVERY_RECOVER, &mddev->recovery)) {
rcu_read_lock();
rdev_for_each_rcu(rdev, mddev)
- if (rdev->raid_disk >= 0 &&
- mddev->delta_disks >= 0 &&
- !test_bit(Journal, &rdev->flags) &&
- !test_bit(Faulty, &rdev->flags) &&
- !test_bit(In_sync, &rdev->flags) &&
- rdev->recovery_offset < mddev->curr_resync)
+ if (mddev->delta_disks >= 0 &&
+ rdev_needs_recovery(rdev, mddev->curr_resync))
rdev->recovery_offset = mddev->curr_resync;
rcu_read_unlock();
}
--
2.39.2
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH v4 2/2] md: fix sync_action incorrect display during resync
2025-08-16 0:25 [PATCH v4 0/2] md: fix sync_action show Zheng Qixing
2025-08-16 0:25 ` [PATCH v4 1/2] md: add helper rdev_needs_recovery() Zheng Qixing
@ 2025-08-16 0:25 ` Zheng Qixing
2025-08-16 0:53 ` [PATCH v4 0/2] md: fix sync_action show Yu Kuai
2 siblings, 0 replies; 4+ messages in thread
From: Zheng Qixing @ 2025-08-16 0:25 UTC (permalink / raw)
To: song, yukuai3, linan122
Cc: linux-raid, linux-kernel, yi.zhang, yangerkun, houtao1,
zhengqixing, pmenzel
From: Zheng Qixing <zhengqixing@huawei.com>
During raid resync, if a disk becomes faulty, the operation is
briefly interrupted. The MD_RECOVERY_RECOVER flag triggered by
the disk failure causes sync_action to incorrectly show "recover"
instead of "resync". The same issue affects reshape operations.
Reproduction steps:
mdadm -Cv /dev/md1 -l1 -n4 -e1.2 /dev/sd{a..d} // -> resync happended
mdadm -f /dev/md1 /dev/sda // -> resync interrupted
cat sync_action
-> recover
Add progress checks in md_sync_action() for resync/recover/reshape
to ensure the interface correctly reports the actual operation type.
Fixes: 4b10a3bc67c1 ("md: ensure resync is prioritized over recovery")
Signed-off-by: Zheng Qixing <zhengqixing@huawei.com>
---
drivers/md/md.c | 37 +++++++++++++++++++++++++++++++++++--
1 file changed, 35 insertions(+), 2 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 3fcb061dd713..9322d9f687b8 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -4844,9 +4844,33 @@ static bool rdev_needs_recovery(struct md_rdev *rdev, sector_t sectors)
rdev->recovery_offset < sectors;
}
+static enum sync_action md_get_active_sync_action(struct mddev *mddev)
+{
+ struct md_rdev *rdev;
+ bool is_recover = false;
+
+ if (mddev->resync_offset < MaxSector)
+ return ACTION_RESYNC;
+
+ if (mddev->reshape_position != MaxSector)
+ return ACTION_RESHAPE;
+
+ rcu_read_lock();
+ rdev_for_each_rcu(rdev, mddev) {
+ if (rdev_needs_recovery(rdev, MaxSector)) {
+ is_recover = true;
+ break;
+ }
+ }
+ rcu_read_unlock();
+
+ return is_recover ? ACTION_RECOVER : ACTION_IDLE;
+}
+
enum sync_action md_sync_action(struct mddev *mddev)
{
unsigned long recovery = mddev->recovery;
+ enum sync_action active_action;
/*
* frozen has the highest priority, means running sync_thread will be
@@ -4870,8 +4894,17 @@ enum sync_action md_sync_action(struct mddev *mddev)
!test_bit(MD_RECOVERY_NEEDED, &recovery))
return ACTION_IDLE;
- if (test_bit(MD_RECOVERY_RESHAPE, &recovery) ||
- mddev->reshape_position != MaxSector)
+ /*
+ * Check if any sync operation (resync/recover/reshape) is
+ * currently active. This ensures that only one sync operation
+ * can run at a time. Returns the type of active operation, or
+ * ACTION_IDLE if none are active.
+ */
+ active_action = md_get_active_sync_action(mddev);
+ if (active_action != ACTION_IDLE)
+ return active_action;
+
+ if (test_bit(MD_RECOVERY_RESHAPE, &recovery))
return ACTION_RESHAPE;
if (test_bit(MD_RECOVERY_RECOVER, &recovery))
--
2.39.2
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v4 0/2] md: fix sync_action show
2025-08-16 0:25 [PATCH v4 0/2] md: fix sync_action show Zheng Qixing
2025-08-16 0:25 ` [PATCH v4 1/2] md: add helper rdev_needs_recovery() Zheng Qixing
2025-08-16 0:25 ` [PATCH v4 2/2] md: fix sync_action incorrect display during resync Zheng Qixing
@ 2025-08-16 0:53 ` Yu Kuai
2 siblings, 0 replies; 4+ messages in thread
From: Yu Kuai @ 2025-08-16 0:53 UTC (permalink / raw)
To: Zheng Qixing, song, yukuai3, linan122
Cc: linux-raid, linux-kernel, yi.zhang, yangerkun, houtao1,
zhengqixing, pmenzel
在 2025/8/16 8:25, Zheng Qixing 写道:
> From: Zheng Qixing <zhengqixing@huawei.com>
>
> Changes in v4:
> Move "rdev->raid_disk >= 0" into rdev_needs_recovery().
>
> Changes in v3:
> Code style modification in patch 1.
>
> Fix incorrect display of sync_action when raid is in resync.
>
> Zheng Qixing (2):
> md: add helper rdev_needs_recovery()
> md: fix sync_action incorrect display during resync
>
> drivers/md/md.c | 60 ++++++++++++++++++++++++++++++++++++++-----------
> 1 file changed, 47 insertions(+), 13 deletions(-)
Applied to md-6.17
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-08-16 0:53 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-16 0:25 [PATCH v4 0/2] md: fix sync_action show Zheng Qixing
2025-08-16 0:25 ` [PATCH v4 1/2] md: add helper rdev_needs_recovery() Zheng Qixing
2025-08-16 0:25 ` [PATCH v4 2/2] md: fix sync_action incorrect display during resync Zheng Qixing
2025-08-16 0:53 ` [PATCH v4 0/2] md: fix sync_action show Yu Kuai
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).