From: Christian Hesse <list@eworm.de>
To: linux-lvm@redhat.com
Cc: Christian Hesse <mail@eworm.de>
Subject: [linux-lvm] [PATCH 1/1] pvscan: wait for udevd
Date: Thu, 11 Feb 2021 12:16:23 +0100 [thread overview]
Message-ID: <20210211111623.34968-1-list@eworm.de> (raw)
From: Christian Hesse <mail@eworm.de>
Running the scan before udevd finished startup may result in failure.
This has been reported for Arch Linux [0] and proper ordering fixes
the issue.
[0] https://bugs.archlinux.org/task/69611
Signed-off-by: Christian Hesse <mail@eworm.de>
---
scripts/lvm2-pvscan.service.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/lvm2-pvscan.service.in b/scripts/lvm2-pvscan.service.in
index 09753e8c9..7b4ace551 100644
--- a/scripts/lvm2-pvscan.service.in
+++ b/scripts/lvm2-pvscan.service.in
@@ -4,6 +4,7 @@ Documentation=man:pvscan(8)
DefaultDependencies=no
StartLimitIntervalSec=0
BindsTo=dev-block-%i.device
+After=systemd-udevd.service
Before=shutdown.target
Conflicts=shutdown.target
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next reply other threads:[~2021-02-11 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 11:16 Christian Hesse [this message]
[not found] ` <f18dff7a-050a-d41d-c643-4616522ba4a0@suse.com>
2021-02-17 8:22 ` [linux-lvm] [PATCH 1/1] pvscan: wait for udevd 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
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=20210211111623.34968-1-list@eworm.de \
--to=list@eworm.de \
--cc=linux-lvm@redhat.com \
--cc=mail@eworm.de \
/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).