archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: Martin Wilck <>,
	LVM general discussion and development <>,
	David Teigland <>
Cc: Oleksandr Natalenko <>,,
	Christian Hesse <>,
	Heming Zhao <>
Subject: Re: [linux-lvm] [PATCH 1/1] pvscan: wait for udevd
Date: Mon, 22 Feb 2021 10:57:27 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 21. 02. 21 v 21:23 Martin Wilck napsal(a):
> On Fri, 2021-02-19 at 23:47 +0100, Zdenek Kabelac wrote:
>> Right time is when switch is finished and we have rootfs with /usr
>> available - should be ensured by  lvm2-monitor.service and it
>> dependencies.
> While we're at it - I'm wondering why dmeventd is started so early. dm-
> event.service on recent installments has only "Requires=dm-
> event.socket", so it'll be started almost immediately after switching
> root. In particular, it doesn't wait for any sort of device
> initialization or udev initialization.


Dmeventd alone does not depend on lvm2 in any way - it's the lvm2 plugin which 
then does all the 'scanning' for VGs/LVs and gets loaded when lvm2 connects to 
monitoring socket. That's also why dmeventd belongs to dm subsystem.

Dmeventd is nothing else then a process to check DM devices periodically - and 
can be used by i.e. dmraid or others...

So as such it doesn't need any devices - but it needs to be initialized early 
so it can accept connections from tools like lvm2 and starts to monitor a 
device without delaying command (as lvm2 wait for confirmation device is 

> 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 

But we want to switch to monitoring ASAP when we switch to rootfs - so the 
'unmonitored' window is as small as possible - there are still same 'grey' 
areas in the correct logic thought...


linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2021-02-22  9:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 11:16 Christian Hesse
     [not found] ` <>
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 [this message]
2021-02-22 13:04                   ` Christian Hesse
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [linux-lvm] [PATCH 1/1] pvscan: wait for udevd' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).