unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Csepp <raingloom@riseup.net>
Cc: 66014@debbugs.gnu.org, Lars Rustand <rustand.lars@gmail.com>
Subject: bug#66014: Unable to use UUIDs to construct RAID array in mapped-devices
Date: Mon, 18 Sep 2023 23:47:10 +0200	[thread overview]
Message-ID: <87ttrrf929.fsf@gnu.org> (raw)
In-Reply-To: <cuc1qevpt05.fsf@riseup.net> (Csepp's message of "Mon, 18 Sep 2023 14:24:16 +0200")

Hi,

Csepp <raingloom@riseup.net> skribis:

> Lars Rustand <rustand.lars@gmail.com> writes:

[...]

>> But this one fails:
>>
>>   (mapped-devices
>>     (list
>>       (mapped-device
>>         (source (list (uuid "a07c54da-eb61-4135-86b8-8791e863e46a") (uuid "c40026af-ace9-47fc-9d3f-4b8d6a2219cb")))
>>         (target "/dev/md0")
>>         (type raid-device-mapping))))
>>
>> The error message I get is guix system: error: #<<uuid> type: dce bv: #vu8(160 124 84 218 235 97 65 53 134 184 135 145 232 99 228 106)>: invalid G-expression input
>>
>> [[End of PGP Signed Part]]
>
> Would it be possible to use /dev/disk/by-uuid paths instead of uuid
> objects for these?

Depends: /dev/disk/by-uuid is populated by eudev, which is not running
at the time initrd code runs; IOW it’s OK to use /dev/disk/by-uuid if
and only if the mapped device is not “needed for boot”.

> I think this big "typeof" based dynamic dispatch that we're using in
> Scheme is erm, not very robust, to put it mildly.

Yeah, it’s not great.  What would you suggest?

Ludo’.




  reply	other threads:[~2023-09-18 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 18:27 bug#66014: Unable to use UUIDs to construct RAID array in mapped-devices Lars Rustand
2023-09-18 12:24 ` Csepp
2023-09-18 21:47   ` Ludovic Courtès [this message]
2023-09-19 10:48     ` Csepp

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=87ttrrf929.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=66014@debbugs.gnu.org \
    --cc=raingloom@riseup.net \
    --cc=rustand.lars@gmail.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.
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).