unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Volf <wolf@wolfsden.cz>
To: 65177@debbugs.gnu.org
Subject: bug#65177: udevd error with lvm-raid array leading to race
Date: Tue, 31 Oct 2023 19:38:09 +0100	[thread overview]
Message-ID: <ZUFJkQsH7TbjS62u@ws> (raw)
In-Reply-To: <58f0d91f-deb8-35c3-d1f3-2ad8a99843c0@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

Hi,

I think the patch is wrong.  No comment regarding the udev rule itself (I do not know much about it), it does spam the logs with:

Oct 31 18:31:35 localhost vmunix: [   60.013538] udevd[327]: invalid key/value pair in file /gnu/store/a3xvv1zxzyb53r5r752q8nh9v9vd150h-udev-rules/69-dm-lvm.rules on line 78, starting at character 1 ('I')
Oct 31 18:31:35 localhost vmunix: [   60.013544] udevd[327]: invalid key/value pair in file /gnu/store/a3xvv1zxzyb53r5r752q8nh9v9vd150h-udev-rules/69-dm-lvm.rules on line 79, starting at character 32 (',')

The fix[0] for that is fairly trivial.

0: https://git.sr.ht/~graywolf/guix/commit/207794679281c1e7e5f2051719fe5c705506eb23

Have a nice day,
W.

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-10-31 19:17 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
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 ` Tomas Volf [this message]
2023-11-02 12:16   ` bug#65177: udevd error with lvm-raid array leading to race 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=ZUFJkQsH7TbjS62u@ws \
    --to=wolf@wolfsden.cz \
    --cc=65177@debbugs.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).