From: Jes Sorensen <jes@trained-monkey.org>
To: Lidong Zhong <lidong.zhong@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH v2] Detail: show correct raid level when the array is inactive
Date: Wed, 14 Oct 2020 11:19:58 -0400 [thread overview]
Message-ID: <48f8cd25-d872-e306-a544-e31c59d91c9b@trained-monkey.org> (raw)
In-Reply-To: <20200914025218.7197-1-lidong.zhong@suse.com>
On 9/13/20 10:52 PM, Lidong Zhong wrote:
> Sometimes the raid level in the output of `mdadm -D /dev/mdX` is
> misleading when the array is in inactive state. Here is a testcase for
> introduction.
> 1\ creating a raid1 device with two disks. Specify a different hostname
> rather than the real one for later verfication.
>
> node1:~ # mdadm --create /dev/md0 --homehost TESTARRAY -o -l 1 -n 2 /dev/sdb
> /dev/sdc
> 2\ remove one of the devices and reboot
> 3\ show the detail of raid1 device
>
> node1:~ # mdadm -D /dev/md127
> /dev/md127:
> Version : 1.2
> Raid Level : raid0
> Total Devices : 1
> Persistence : Superblock is persistent
> State : inactive
> Working Devices : 1
>
> You can see that the "Raid Level" in /dev/md127 is raid0 now.
> After step 2\ is done, the degraded raid1 device is recognized
> as a "foreign" array in 64-md-raid-assembly.rules. And thus the
> timer to activate the raid1 device is not triggered. The array
> level returned from GET_ARRAY_INFO ioctl is 0. And the string
> shown for "Raid Level" is
> str = map_num(pers, array.level);
> And the definition of pers is
> mapping_t pers[] = {
> { "linear", LEVEL_LINEAR},
> { "raid0", 0},
> { "0", 0}
> ...
> So the misleading "raid0" is shown in this testcase.
>
> Changelog:
> v1: don't show "Raid Level" when array is inactive
> Signed-off-by: Lidong Zhong <lidong.zhong@suse.com>
>
Applied!
Thanks,
Jes
next prev parent reply other threads:[~2020-10-14 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 2:52 [PATCH v2] Detail: show correct raid level when the array is inactive Lidong Zhong
2020-10-14 15:19 ` Jes Sorensen [this message]
2020-10-20 9:50 ` Tkaczyk, Mariusz
2020-10-20 12:32 ` Tkaczyk, Mariusz
2020-11-22 13:15 ` Zhong Lidong
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=48f8cd25-d872-e306-a544-e31c59d91c9b@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=lidong.zhong@suse.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).