unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
To: Michael Rohleder <mike@rohleder.de>
Cc: help-guix@gnu.org
Subject: Re: What LVM support is missing?
Date: Wed, 06 May 2020 09:40:43 +0200	[thread overview]
Message-ID: <877dxptssk.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87bln33bbu.fsf@rohleder.de> (Michael Rohleder's message of "Mon,  04 May 2020 18:37:57 +0200")

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

Michael Rohleder <mike@rohleder.de> writes:

> Hey Simon!
>
> Simon Josefsson <simon@josefsson.org> writes:
>> I'm thinking that having the root file system on LVM may be unsupported,
>> so that manual could say that, but I'm not even sure that is true.  I
>> haven't tried it though.  Perhaps 'lvm2' should be pre-installed on the
>> default installation image to help move LVM support along.
>>
>> Another thought may be that constructing LVM partitions through the
>> mapped-device mechanism is not supported:
>>
>> http://guix.gnu.org/manual/en/html_node/Mapped-Devices.html
>>
>> however as far as I can tell, LVM is working just as well as LUKS/RAID
>> here: LVM just doesn't need any command to start the devices.  The
>> mapped-device approach appear to require out-of-band device creation for
>> LUKS and RAID, just like is required for LVM.  A no-op
>> `lvm-device-mapping' could be added for completeness, and it might run
>> 'pvscan --active ay' or something like that if we really wanted to but
>> I'm not sure when that would be useful.
>
> I use a root fs on lvm.
> What helped me a lot was this posting, where I stole most things:
>
> https://lists.gnu.org/archive/html/bug-guix/2020-02/msg00285.html

Thanks for pointer!  Maybe some examples like this could be added to the
manual.  I'll experiment a bit too and see if I can propose something...

> What (currrently) isnt working is the lvm device-mapper and (for me more
> important) lvmcache...

What do you expect from a lvm device-mapper?  When I thought about it,
it is mostly a no-op since the kernel handles this automatically, or?

Working lvmcache does not seem required to claim support for LVM to me.
Why doesn't lvmcache work?  Also sometimes the performance improvements
doesn't seem that significant:
http://strugglers.net/~andy/blog/2017/07/19/bcache-and-lvmcache/

/Simon

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

      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
2020-05-04 16:37 ` Michael Rohleder
2020-05-06  7:40   ` Simon Josefsson [this message]

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=877dxptssk.fsf@latte.josefsson.org \
    --to=simon@josefsson.org \
    --cc=help-guix@gnu.org \
    --cc=mike@rohleder.de \
    /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).