From: Shaohua Li <shli@kernel.org>
To: Lidong Zhong <lzhong@suse.com>, jes.sorensen@gmail.com
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] md: change the initialization value for a spare device spot to MD_DISK_ROLE_SPARE
Date: Tue, 13 Jun 2017 10:17:08 -0700 [thread overview]
Message-ID: <20170613171708.roims6ja6vtuwwlo@kernel.org> (raw)
In-Reply-To: <20170612024555.1120-1-lzhong@suse.com>
On Mon, Jun 12, 2017 at 10:45:55AM +0800, Lidong Zhong wrote:
> The value for spare spot of sb->dev_roles is changed from
> MD_DISK_ROLE_FAULTY to MD_DISK_ROLE_SPARE to keep align
> with the value when the superblock is firstly created in
> userspace.
Could you point out where mdadm does this?
I'm wondering what's the impact here. If there is a disk, we will set correct
role at the end of super_1_sync(), otherwise faulty sounds more reasonable.
Jes,
Could you help check this?
Thanks,
Shaohua
> Signed-off-by: Lidong Zhong <lzhong@suse.com>
> ---
> drivers/md/md.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 87edc342ccb3..a9aacedefbca 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -1852,7 +1852,7 @@ static void super_1_sync(struct mddev *mddev, struct md_rdev *rdev)
> max_dev = le32_to_cpu(sb->max_dev);
>
> for (i=0; i<max_dev;i++)
> - sb->dev_roles[i] = cpu_to_le16(MD_DISK_ROLE_FAULTY);
> + sb->dev_roles[i] = cpu_to_le16(MD_DISK_ROLE_SPARE);
>
> if (test_bit(MD_HAS_JOURNAL, &mddev->flags))
> sb->feature_map |= cpu_to_le32(MD_FEATURE_JOURNAL);
> --
> 2.12.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-13 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 2:45 [PATCH] md: change the initialization value for a spare device spot to MD_DISK_ROLE_SPARE Lidong Zhong
2017-06-13 17:17 ` Shaohua Li [this message]
2017-06-14 3:16 ` Lidong Zhong
2017-06-15 17:02 ` Shaohua Li
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=20170613171708.roims6ja6vtuwwlo@kernel.org \
--to=shli@kernel.org \
--cc=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lzhong@suse.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