From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Adrien 'neox' Bourmault <neox@gnu.org>, 65177@debbugs.gnu.org
Cc: Tobias Geerinckx-Rice <me@tobias.gr>
Subject: bug#65177: udevd error with lvm-raid array leading to race condition with luks
Date: Thu, 10 Aug 2023 10:02:22 +0200 [thread overview]
Message-ID: <87ttt7e35d.fsf@jpoiret.xyz> (raw)
In-Reply-To: <58f0d91f-deb8-35c3-d1f3-2ad8a99843c0@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
Hi Adrien,
Adrien 'neox' Bourmault <neox@gnu.org> writes:
> Aug 9 11:40:27 localhost vmunix: [ 7.525877] udevd[515]: failed
> to execute '/usr/bin/systemd-run' '/usr/bin/systemd-run --no-block
> --property DefaultDependencies=no --unit lvm-activate-HOMERAID
> /gnu/store/hffkn63zx2zjadawrkxpnr486frc9n74-lvm2-2.03.21/sbin/lvm
> vgchange -aay --autoactivation event HOMERAID': No such file or directory
Since lvm2 2.03.14, the included udev rules use systemd-run to run
vgchange and activate the volume group. lvm2 was updated recently from
2.03.11 to 2.03.21, then 2.03.22 (cc'ing tobias), and probably started
exhibiting this behavior then. I think we can probably remove the
indirection through systemd-run and directly run vgchange.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-08-10 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 10:25 bug#65177: udevd error with lvm-raid array leading to race condition with luks Adrien 'neox' Bourmault
2023-08-10 8:02 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-09-14 9:25 ` Yann Dupont
2023-09-14 16:23 ` Yann Dupont
2023-09-25 7:35 ` Simon Tournier
2023-10-17 9:00 ` Simon Tournier
2023-10-31 8:59 ` Simon Tournier
2023-10-31 18:38 ` bug#65177: udevd error with lvm-raid array leading to race Tomas Volf
2023-11-02 12:16 ` Simon Tournier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttt7e35d.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=65177@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=me@tobias.gr \
--cc=neox@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).