From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where did lvm installation guide go?
Date: Fri, 30 Aug 2013 09:13:16 -0500 [thread overview]
Message-ID: <CADPrc80OgNpr8Zot1o101x7syv+aRNT8ogroRt-Zc3byW09xtQ@mail.gmail.com> (raw)
In-Reply-To: <52203746.3090203@gmail.com>
On Fri, Aug 30, 2013 at 1:10 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 30/08/2013 07:36, Canek Peláez Valdés wrote:
>> On Fri, Aug 30, 2013 at 12:21 AM, J. Roeleveld <joost@antarean.org> wrote:
>>> gottlieb@nyu.edu wrote:
>>>> On Thu, Aug 29 2013, Canek Peláez Valdés wrote:
>>>>
>>>>> On Thu, Aug 29, 2013 at 4:19 PM, <gottlieb@nyu.edu> wrote:
>>>>>>
>>>>>> I have experience with LVM, but not systemd or dracut or initramfs
>>>>>>
>>>>>> * both grub and grub2 support lvm
>>>>>
>>>>> Does GRUB legacy handles /boot in LVM? I haven't tried that yet.
>>>>
>>>> That I don't know. I believe the LVM "companion manual" that I am
>>>> seeking and that I used for previous installs advised against /boot on
>>>> lvm (probably also /lib and others). Perhaps this was simply
>>>> reflecting
>>>> no initramfs. Hence any grub issue with /boot on lvm didn't arise.
>>>>
>>>> allan
>>>
>>> No.
>>>
>>> Grub legacy does not support LVM for the /boot.
>>> That's why I have it there.
>>>
>>> UEFI only understands FAT. Which means you need to have a boot partition
>>> outside of LVM for that.
>>
>> Good to know, thanks. Another reason not to use LVM I guess.
>
> Why not use LVM?
I just don't see the point. I have never used it, and now that I have
a test system, I don't see any advantage for my particular use cases.
> Yes, it is some added complexity you need to understand but it stays out
> of your way till you need it, doesn't affect disk efficiency in any
> significant way and just works. When you need the services it offers
> they are there and until then just use mkfs and mount the block device
> it offers.
My point exactly; I have never needed its services in 18 years using
Linux (servers and workstation). Again, in my use cases.
> Unless you have all your filesystems part of / itself, you run the risk
> of hitting hard limits rapidly and LVM gives you a proper way to deal
> with that, unlike using rigid partitions directly. I see a small amount
> of new code to understand followed by huge benefits.
I understand the code all right, as I commented to Allan I had no
problems installing a systemd+LVM machine (with even /boot in LVM). I
just don't see the benefits (in my use cases).
> The best way to deal with this actual issue is the ZFS/btrfs approach
> but those aren't usable for the masses yet, whereas LVM is.
btrfs sounds cool (specially in SSD), but I'm also waiting for it to
be stable enough.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2013-08-30 14:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 15:47 [gentoo-user] where did lvm installation guide go? gottlieb
2013-08-29 16:56 ` [gentoo-user] " James
2013-08-29 21:02 ` gottlieb
2013-08-29 17:29 ` [gentoo-user] " Canek Peláez Valdés
2013-08-29 21:19 ` gottlieb
2013-08-30 0:30 ` Canek Peláez Valdés
2013-08-30 1:45 ` gottlieb
2013-08-30 2:29 ` Canek Peláez Valdés
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 5:36 ` Canek Peláez Valdés
2013-08-30 6:10 ` Alan McKinnon
2013-08-30 7:16 ` Dale
2013-08-30 14:05 ` Tanstaafl
2013-08-30 14:28 ` Canek Peláez Valdés
2013-08-30 14:37 ` Tanstaafl
2013-08-30 14:38 ` Alan McKinnon
2013-08-30 14:59 ` Tanstaafl
2013-08-30 14:56 ` Canek Peláez Valdés
2013-08-31 11:31 ` [gentoo-user] " Nicolas Sebrecht
2013-08-30 14:13 ` Canek Peláez Valdés [this message]
2013-08-30 5:47 ` [gentoo-user] " Alan McKinnon
2013-08-30 7:17 ` Dale
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 6:13 ` Alan McKinnon
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 5:20 ` J. Roeleveld
2013-08-30 15:18 ` gottlieb
2013-08-30 16:48 ` joost
2013-08-30 19:18 ` Alan McKinnon
2013-08-31 14:18 ` gottlieb
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADPrc80OgNpr8Zot1o101x7syv+aRNT8ogroRt-Zc3byW09xtQ@mail.gmail.com \
--to=caneko@gmail.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox