From: Christian Hesse <list@eworm.de>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: Natalenko <oleksandr@redhat.com>,
linux-lvm@e1890.dsca.akamaiedge.net, Oleksandr,
David Teigland <teigland@redhat.com>,
LVM general discussion and development <linux-lvm@redhat.com>,
Martin Wilck <mwilck@suse.com>,
Heming Zhao <heming.zhao@suse.com>
Subject: Re: [linux-lvm] [PATCH 1/1] pvscan: wait for udevd
Date: Mon, 22 Feb 2021 14:04:17 +0100 [thread overview]
Message-ID: <20210222140417.4f890bec@leda> (raw)
In-Reply-To: <bcb2eb82-46b3-8e6b-c9b6-56442b4f63a3@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1572 bytes --]
Zdenek Kabelac <zkabelac@redhat.com> on Mon, 2021/02/22 10:57:
> > I've gone through the various tasks that dmeventd is responsible for,
> > and I couldn't see anything that'd be strictly necessary during early
> > boot. I may be overlooking something of course. Couldn't the monitoring
>
> As said - during ramdisk boot - monitor shall not be used (AFAIK - dracut
> is supposed to use disabled monitoring in it's modified copy of lvm.conf
> within ramdisk)
I could not find anything in dracut that modifies lvm.conf, but looks like
dracut calls the lvm commands with `--ignoremonitoring`.
To date this is not handled in lvm2's mkinitcpio hook... Wondering if
that would help. Oleksandr, you could undo the udev workaround, then apply
the following diff to /usr/lib/initcpio/install/lvm2, regenerate the
initramfs and retry?
--- lvm2_install (revision 408582)
+++ lvm2_install (working copy)
@@ -34,6 +34,7 @@
add_file "/usr/lib/udev/rules.d/95-dm-notify.rules"
add_file "/usr/lib/initcpio/udev/11-dm-initramfs.rules" "/usr/lib/udev/rules.d/11-dm-initramfs.rules"
add_file "/etc/lvm/lvm.conf"
+ sed -i '/^\smonitoring =/s/1/0/' "${BUILDROOT}/etc/lvm/lvm.conf"
# this udev rule is specific for systemd and non-systemd systems
if command -v add_systemd_unit >/dev/null; then
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
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:[~2021-02-22 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 11:16 [linux-lvm] [PATCH 1/1] pvscan: wait for udevd Christian Hesse
[not found] ` <f18dff7a-050a-d41d-c643-4616522ba4a0@suse.com>
2021-02-17 8:22 ` Martin Wilck
[not found] ` <20210217130329.7de41147@leda>
2021-02-17 13:38 ` Oleksandr Natalenko
2021-02-18 15:19 ` Martin Wilck
2021-02-18 15:30 ` Oleksandr Natalenko
2021-02-19 9:22 ` Martin Wilck
2021-02-19 16:37 ` David Teigland
2021-02-19 22:47 ` Zdenek Kabelac
2021-02-21 20:23 ` Martin Wilck
2021-02-22 9:57 ` Zdenek Kabelac
2021-02-22 13:04 ` Christian Hesse [this message]
2021-02-25 16:51 ` Oleksandr Natalenko
2021-02-21 20:26 ` Martin Wilck
2021-02-17 13:49 ` Martin Wilck
2021-02-17 19:11 ` Oleksandr Natalenko
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=20210222140417.4f890bec@leda \
--to=list@eworm.de \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@e1890.dsca.akamaiedge.net \
--cc=linux-lvm@redhat.com \
--cc=mwilck@suse.com \
--cc=oleksandr@redhat.com \
--cc=teigland@redhat.com \
--cc=zkabelac@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).