All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:39:06 -0500	[thread overview]
Message-ID: <566AFC2A.7040009@turmel.org> (raw)
In-Reply-To: <CABdHLQ4++kTu22YGkdDW3r1UAxf_7E_+fcn9SfFnTSg6MgSm9w@mail.gmail.com>

On 12/11/2015 11:32 AM, P. Remek wrote:
>> It's likely that the udev rules that drive incremental assembly don't
>> have the mapper aliases at the moment they run.  Try:
>>
>> DEVICE /dev/dm*
> 
> That crossed my mind too, but no, this doesn't help, the array still
> doesn't show up

Next step would be to run udevadm trigger while running udevadm monitor
in another session right after boot to see what events run and what
rules are executed.  That should help narrow this down.  Also compare
dmesg from boot with dmesg from udevadm trigger.

I'm not familiar enough with ubuntu to be much more help.

  reply	other threads:[~2015-12-11 16:39 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
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 [this message]
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=566AFC2A.7040009@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.