From: Roger Heflin <rogerheflin@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Peter Rajnoha <prajnoha@redhat.com>,
Martin Wilck <mwilck@suse.com>,
Heming Zhao <heming.zhao@suse.com>
Subject: Re: [linux-lvm] LVM autoactivation and udev
Date: Wed, 9 Mar 2022 11:07:13 -0600 [thread overview]
Message-ID: <CAAMCDedvvBpq3jt6A=+OruDpnwu5qsgRZbU+JFt3PSPq4L4WnQ@mail.gmail.com> (raw)
In-Reply-To: <20220309162711.GA5819@redhat.com>
On Wed, Mar 9, 2022 at 10:35 AM David Teigland <teigland@redhat.com> wrote:
>
>
> - if all three of those don't catch it, then filter-mpath will also
> check if the component wwid is listed in /etc/multipath/wwids and
> ignore the device if it is.
>
> If all four of those methods fail to exclude a multipath component, then
> an LV could be activated using the component. While this isn't good, it
> can be corrected by running lvchange --refresh. I'd like to get any
> details of that happening to see if we can improve it.
>
I have also had luck with making sure multipath is in the initramfs,
and adding rd.lvm.vg=<rootvgnameneededforboot> on the kernel boot line
so that in the initramfs only the VG needed for boot up is started up
early inside the initramfs. That has typically let multipathd
inside the initrd grab any other devices and configure them for
multipath before LVM activates them.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-03-09 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 15:29 [linux-lvm] LVM autoactivation and udev Martin Wilck
2022-03-09 16:27 ` David Teigland
2022-03-09 17:04 ` Martin Wilck
2022-03-09 17:26 ` David Teigland
2022-03-09 19:48 ` Martin Wilck
[not found] ` <1f49866ba907896dc3678b47c5bb68d87e28b3c1.camel@suse.com>
2022-03-09 20:07 ` David Teigland
2022-03-09 17:07 ` Roger Heflin [this message]
2022-03-09 17:17 ` Martin Wilck
2022-03-21 8:57 ` heming.zhao
2022-03-21 16:44 ` David Teigland
2022-03-23 7:33 ` heming.zhao
2022-03-23 7:51 ` Martin Wilck
2022-03-24 8:26 ` heming.zhao
2022-03-24 9:02 ` Martin Wilck
2022-03-24 19:01 ` David Teigland
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='CAAMCDedvvBpq3jt6A=+OruDpnwu5qsgRZbU+JFt3PSPq4L4WnQ@mail.gmail.com' \
--to=rogerheflin@gmail.com \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@redhat.com \
--cc=mwilck@suse.com \
--cc=prajnoha@redhat.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).