From: Phil Turmel <philip@turmel.org>
To: "P. Remek" <p.remek1@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: start dm-multipath before mdadm raid
Date: Fri, 11 Dec 2015 09:04:26 -0500 [thread overview]
Message-ID: <566AD7EA.4070903@turmel.org> (raw)
In-Reply-To: <CABdHLQ4rh+Rtu6U+ZX6m0CWXu3sW4boEzHaPdxD03UBf82EJcQ@mail.gmail.com>
On 12/10/2015 05:44 PM, P. Remek wrote:
>>
>> Order of device discovery is not guaranteed, but base devices will
>> almost always show up before multipath devices. You have to filter out
>> the base devices from mdadm consideration:
>>
>> Add a DEVICES statement to your mdadm.conf that only matches your
>> multipath device names, not the base names. Then update your initramfs
>> so it applies to early boot as well.
>>
>
>
> This is something which I actually already tried. I specified in my
> /etc/mdadm/mdadm.conf following:
>
> DEVICE /dev/mapper/hgst-ssd*
>
> In my /etc/multipath.conf I instruct dm-multipath to create
> /dev/mapper/hgst-ssd1 /dev/mapper/hgst-ssd2 /dev/mapper/hgst-ssd3
You haven't said that you've updated your initramfs with this info.
> But the only result is that after this config, the md raid is not
> started at all. My conclusion was that when md raid was starting, the
> multipath devices did not yet exist so it did not start up the array.
That would be an initramfs bug, most likely. Modern initramfs like
dracut use incremental assembly to start arrays and subsystems as
devices are started, regardless what order they show up.
Phil
next prev parent reply other threads:[~2015-12-11 14:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 15:29 start dm-multipath before mdadm raid P. Remek
2015-12-10 16:28 ` John Stoffel
2015-12-10 22:50 ` P. Remek
2015-12-11 18:10 ` P. Remek
2015-12-10 16:55 ` Phil Turmel
2015-12-10 22:44 ` P. Remek
2015-12-11 14:04 ` Phil Turmel [this message]
2015-12-11 16:01 ` P. Remek
2015-12-11 16:08 ` Phil Turmel
2015-12-11 16:32 ` P. Remek
2015-12-11 16:39 ` Phil Turmel
2015-12-11 17:57 ` P. Remek
2015-12-11 19:30 ` John Stoffel
2015-12-12 19:17 ` P. Remek
2015-12-15 15:00 ` P. Remek
2015-12-15 15:07 ` Phil Turmel
2015-12-15 15:42 ` John Stoffel
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=566AD7EA.4070903@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=p.remek1@googlemail.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).