From: Simon Josefsson <simon@josefsson.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix@gnu.org
Subject: Re: What LVM support is missing?
Date: Wed, 06 May 2020 09:33:53 +0200 [thread overview]
Message-ID: <87bln1tt3y.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87368f1y12.fsf@devup.no> (Marius Bakke's message of "Mon, 04 May 2020 18:10:33 +0200")
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
Marius Bakke <mbakke@fastmail.com> writes:
> Simon Josefsson <simon@josefsson.org> writes:
>
>> The manual is quite clear that LVM support is missing:
>>
>> https://guix.gnu.org/manual/en/html_node/Limitations.html
>>
>> This held me back from using guix as the OS for my virtualization
>> servers since I use LVM for virtual machines. However, one evening I
>> was curious how difficult it would be to fix the above limitation, so I
>> started with a simple 'guix package -i lvm2' and that allowed me to get
>> LVM to work and I can't really notice anything missing.
>>
>> Before producing a patch to correct the manual, could someone explain
>> what LVM support was intended that was missing? Does a reference to LVM
>> as a limitation of Guix still make sense?
>
> What's missing is support in the configuration system: the ability to
> declare a LVM mapped device in the OS configuration and expect 'guix
> system init', 'guix system reconfigure' etc to work.
>
> LVM 2.03 simplifies things a bit, but I don't know of any recent
> attempts to add LVM support to the configuration system.
How is that different than RAID or LUKS support not being available
through that mechanism? I need to run 'mdadm --create' or 'cryptsetup
luksFormat' externally to config.scm too. It appears to me that the
status of LVM is similar o RAID or LUKS wrt the configuration system. I
think people generally regard RAID and LUKS as supported and working by
Guix, right? My point is that the state of LVM support is similar, so
the warning about this limitation may do more harm than good. There
could be some more examples added on how to setup some LVM partitions
and have them be mounted, or even examples of how to put rootfs on LVM,
and with that the prominent warning about missing LVM could be dropped.
/Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-06 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 13:16 What LVM support is missing? Simon Josefsson
2020-05-04 16:10 ` Marius Bakke
2020-05-06 7:33 ` Simon Josefsson [this message]
2020-05-04 16:37 ` Michael Rohleder
2020-05-06 7:40 ` Simon Josefsson
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=87bln1tt3y.fsf@latte.josefsson.org \
--to=simon@josefsson.org \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.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.
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).