reconfigure with mapped-devices broken after e37944d8270cdca5729e3583136c4fe9d487779c?

reconfigure with mapped-devices broken after e37944d8270cdca5729e3583136c4fe9d487779c?

[Alex ter Weele]

Hello!

I guix-pulled to something recent and got an error that was something
like "cannot stat: "my-root"".

My operating-system has sections like:

  (mapped-devices
   (list (mapped-device
          (source (uuid "97c130e9-edf4-40e4-8bfc-88fba056ffce"))
          (target "my-root")
          (type luks-device-mapping))))

  (file-systems (cons (file-system
                        (device "my-root")
                        (mount-point "/")
                        (type "ext4")
                        (dependencies mapped-devices))
                      %base-file-systems))

I guix-pulled to the titular commit and was able to reconfigure
successfully. Did something change in
424cea8083a4cee63290c80235aed61bd12affb1 or near there that could have
caused what I observed?

Re: reconfigure with mapped-devices broken after e37944d8270cdca5729e3583136c4fe9d487779c?

[Ludovic Courtès]

Hi Alex,

Alex ter Weele <alex.ter.weele@gmail.com> skribis:

> I guix-pulled to something recent and got an error that was something
> like "cannot stat: "my-root"".
>
> My operating-system has sections like:
>
>   (mapped-devices
>    (list (mapped-device
>           (source (uuid "97c130e9-edf4-40e4-8bfc-88fba056ffce"))
>           (target "my-root")
>           (type luks-device-mapping))))
>
>   (file-systems (cons (file-system
>                         (device "my-root")
>                         (mount-point "/")
>                         (type "ext4")
>                         (dependencies mapped-devices))

I think you’re missing:

  (title 'label)

in your ‘file-system’ declaration.  As a consequence, “my-root” is
interpreted to be a device file name.

HTH!

Ludo’.

Re: reconfigure with mapped-devices broken after e37944d8270cdca5729e3583136c4fe9d487779c?

[Platoxia]

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

I also encountered this problem with the same update. Previously, following the old example configurations from the GuixSD documentation for encrypting a partition led to a file-system section that excluded the 'title' attribute entirely. I believe this is due to the default for the 'title' parameter being 'device, which used to work fine with simply using the device name, as in (device "my-root").

According to the current manual:

" However, when the source of a file system is a mapped device
   (*note Mapped Devices::), its ‘device’ field _must_ refer to
   the mapped device name—e.g., ‘/dev/mapper/root-partition’—and
   consequently ‘title’ must be set to ‘'device’.  This is
   required so that the system knows that mounting the file
   system depends on having the corresponding device mapping
   established."

As such, the file-system configuration section when using mapped devices should use 'device as the title parameter (or excluded completely since it is still the default), and the absolute path to the device name as the device parameter, as the following example shows:

(file-systems (cons (file-system
                      (title 'device)
                      (device "/dev/mapper/my-root")
                      (mount-point "/")
                      (type "ext4")
                      (dependencies mapped-devices))
                    %base-file-systems))

Platoxia

[-- Attachment #2: Type: text/html, Size: 3686 bytes --]