mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yu Kuai <yukuai@kernel.org>
To: Zheng Qixing <zhengqixing@huaweicloud.com>,
	song@kernel.org, yukuai3@huawei.com, linan122@huawei.com
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	yi.zhang@huawei.com, yangerkun@huawei.com, houtao1@huawei.com,
	zhengqixing@huawei.com
Subject: Re: [PATCH] md: allow removing faulty rdev during resync
Date: Sat, 12 Jul 2025 17:58:10 +0800	[thread overview]
Message-ID: <9b504689-6c9a-48b5-882c-8ddfaf43a801@kernel.org> (raw)
In-Reply-To: <20250707075412.150301-1-zhengqixing@huaweicloud.com>

在 2025/7/7 15:54, Zheng Qixing 写道:

> From: Zheng Qixing <zhengqixing@huawei.com>
>
> During RAID resync, faulty rdev cannot be removed and will result in
> "Device or resource busy" error when attempting hot removal.
>
> Reproduction steps:
>    mdadm -Cv /dev/md0 -l1 -n3 -e1.2 /dev/sd{b..d}
>    mdadm /dev/md0 -f /dev/sdb
>    mdadm /dev/md0 -r /dev/sdb
>    -> mdadm: hot remove failed for /dev/sdb: Device or resource busy
>
> After commit 4b10a3bc67c1 ("md: ensure resync is prioritized over
> recovery"), when a device becomes faulty during resync, the
> md_choose_sync_action() function returns early without calling
> remove_and_add_spares(), preventing faulty device removal.
>
> This patch extracts a helper function remove_spares() to support
> removing faulty devices during RAID resync operations.
>
> Fixes: 4b10a3bc67c1 ("md: ensure resync is prioritized over recovery")
> Signed-off-by: Zheng Qixing <zhengqixing@huawei.com>
> ---
>   drivers/md/md.c | 24 +++++++++++++++++-------
>   1 file changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 0f03b21e66e4..7f5e5a16243a 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c

Applied to md-6.17

Thanks

> @@ -9456,17 +9456,11 @@ static bool md_spares_need_change(struct mddev *mddev)
>   	return false;
>   }
>   
> -static int remove_and_add_spares(struct mddev *mddev,
> -				 struct md_rdev *this)
> +static int remove_spares(struct mddev *mddev, struct md_rdev *this)
>   {
>   	struct md_rdev *rdev;
> -	int spares = 0;
>   	int removed = 0;
>   
> -	if (this && test_bit(MD_RECOVERY_RUNNING, &mddev->recovery))
> -		/* Mustn't remove devices when resync thread is running */
> -		return 0;
> -
>   	rdev_for_each(rdev, mddev) {
>   		if ((this == NULL || rdev == this) && rdev_removeable(rdev) &&
>   		    !mddev->pers->hot_remove_disk(mddev, rdev)) {
> @@ -9480,6 +9474,21 @@ static int remove_and_add_spares(struct mddev *mddev,
>   	if (removed && mddev->kobj.sd)
>   		sysfs_notify_dirent_safe(mddev->sysfs_degraded);
>   
> +	return removed;
> +}
> +
> +static int remove_and_add_spares(struct mddev *mddev,
> +				 struct md_rdev *this)
> +{
> +	struct md_rdev *rdev;
> +	int spares = 0;
> +	int removed = 0;
> +
> +	if (this && test_bit(MD_RECOVERY_RUNNING, &mddev->recovery))
> +		/* Mustn't remove devices when resync thread is running */
> +		return 0;
> +
> +	removed = remove_spares(mddev, this);
>   	if (this && removed)
>   		goto no_add;
>   
> @@ -9522,6 +9531,7 @@ static bool md_choose_sync_action(struct mddev *mddev, int *spares)
>   
>   	/* Check if resync is in progress. */
>   	if (mddev->recovery_cp < MaxSector) {
> +		remove_spares(mddev, NULL);
>   		set_bit(MD_RECOVERY_SYNC, &mddev->recovery);
>   		clear_bit(MD_RECOVERY_RECOVER, &mddev->recovery);
>   		return true;

      parent reply	other threads:[~2025-07-12  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07  7:54 Zheng Qixing
2025-07-07  8:25 ` Li Nan
2025-07-12  9:58 ` Yu Kuai [this message]

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=9b504689-6c9a-48b5-882c-8ddfaf43a801@kernel.org \
    --to=yukuai@kernel.org \
    --cc=houtao1@huawei.com \
    --cc=linan122@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.com \
    --cc=zhengqixing@huawei.com \
    --cc=zhengqixing@huaweicloud.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®