From: Jes Sorensen <jes.sorensen@gmail.com>
To: Zhilong Liu <zlliu@suse.com>, NeilBrown <neilb@suse.com>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: mdadm: question about tests/07autoassemble
Date: Tue, 21 Nov 2017 13:24:22 -0500 [thread overview]
Message-ID: <9af3b82d-33c0-2a2d-5f7c-c25c4a189d19@gmail.com> (raw)
In-Reply-To: <b10c5be1-0b85-320f-9ded-dd8ad533d31c@suse.com>
On 11/08/2017 04:43 AM, Zhilong Liu wrote:
> Hi, Neil and Jes;
> I have a question that which name is mdadm expected, md0 or md127 here?
>
> the case is:
>
> ./mdadm --quiet -CR /dev/md1 -l1 -n2 /dev/loop0 /dev/loop1
> --homehost=testing --auto=yes
> ./mdadm --quiet -CR /dev/md2 -l1 -n2 /dev/loop2 /dev/loop3
> --homehost=testing --auto=yes
> ./mdadm --quiet -CR /dev/md0 -l0 -n2 /dev/md1 /dev/md2
> --homehost=testing --auto=yes
>
> ./mdadm -Ss
> ./mdadm --quiet -As -c /dev/null --homehost=testing -vvv
>
> */linux-apta:~/mdadm-test #/* cat /proc/mdstat
> Personalities : [raid1] [raid0]
> md127 : active raid0 md1[0] md2[1]
> 33792 blocks super 1.2 512k chunks
>
> md2 : active raid1 loop2[0] loop3[1]
> 18944 blocks super 1.2 [2/2] [UU]
>
> md1 : active raid1 loop0[0] loop1[1]
> 18944 blocks super 1.2 [2/2] [UU]
>
> unused devices: <none>
>
> And I have another question, I still don't find "when and where" got the
> name of md127,
> It didn't invoke the find_free_devnm, and I debug with udevadm, still
> confused. would
> you give me some points on it? I would continue to find which code does
> this.
Did you pause between mdadm -Ss and mdadm -As ?
It may be md0 was still in use. You aren't really guaranteed the name,
unless you specify it in /etc/mdadm.conf or on the command line?
Cheers,
Jes
parent reply other threads:[~2017-11-21 18:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <b10c5be1-0b85-320f-9ded-dd8ad533d31c@suse.com>]
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=9af3b82d-33c0-2a2d-5f7c-c25c4a189d19@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=zlliu@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;
as well as URLs for NNTP newsgroup(s).