All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: Julian Andres Klode <julian.klode@canonical.com>,
	Guan Junxiong <guanjunxiong@huawei.com>,
	development mailing list <dm-devel@redhat.com>
Subject: Re: multipath-tools 0.7.4 failure to remove device
Date: Thu, 18 Jan 2018 09:11:02 +0100	[thread overview]
Message-ID: <1516263062.4861.4.camel@suse.com> (raw)
In-Reply-To: <20180118035003.GV5638@octiron.msp.redhat.com>

On Wed, 2018-01-17 at 21:50 -0600, Benjamin Marzinski wrote:

> Now, I don't see how this could cause a boot to fail since this is a
> new
> device that isn't getting set up, but I really never test this,
> because
> when we create the initramfs in RedHat based distros, we edit the
> multipath.conf file in it to blacklist all devices except those
> needed
> by the initramfs.

I'm a bit puzzled. It's against my personcal conviction that the
blacklist must be the same between initrd and root FS. How do you
prevent LVM or other layers grabbing blacklisted devices during
initramfs processing, so that they can't be multipathed any more later?

Martin

-- 
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2018-01-18  8:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12  8:38 multipath-tools 0.7.4 failure to remove device Julian Andres Klode
2018-01-12 20:35 ` Martin Wilck
2018-01-12 21:47   ` Julian Andres Klode
2018-01-12 22:18     ` Martin Wilck
2018-01-12 22:26       ` Julian Andres Klode
2018-01-15 15:44       ` Julian Andres Klode
2018-01-15 16:12         ` Martin Wilck
2018-01-15 16:26           ` Julian Andres Klode
2018-01-15 16:46             ` Martin Wilck
2018-01-16 20:30               ` Benjamin Marzinski
2018-01-16 22:05                 ` Xose Vazquez Perez
2018-01-17  0:43                 ` Martin Wilck
2018-01-17 18:38                   ` Benjamin Marzinski
2018-01-18  3:50                     ` Benjamin Marzinski
2018-01-18  8:11                       ` Martin Wilck [this message]
2018-01-18 15:22                         ` Benjamin Marzinski
2018-01-18 16:32                           ` Martin Wilck
2018-01-17  9:38                 ` Julian Andres Klode
2018-01-17 18:45                   ` Benjamin Marzinski
2018-01-17 16:27                 ` Multipath path classification revisited Martin Wilck
2018-01-18 22:35                   ` Benjamin Marzinski
2018-01-13 19:46     ` multipath-tools 0.7.4 failure to remove device Martin Wilck

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=1516263062.4861.4.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=bmarzins@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=guanjunxiong@huawei.com \
    --cc=julian.klode@canonical.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.