From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where did lvm installation guide go?
Date: Fri, 30 Aug 2013 07:21:07 +0200 [thread overview]
Message-ID: <3d90a1d3-1a1e-4a4c-82b9-e0d34237c103@email.android.com> (raw)
In-Reply-To: <CADPrc82JPq_EoGB-crgWYFk3MMSMVUm8jvn=vMJyJbymBdqMkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3179 bytes --]
"Canek Peláez Valdés" <caneko@gmail.com> wrote:
>On Thu, Aug 29, 2013 at 10:47 AM, <gottlieb@nyu.edu> wrote:
>> I want to reinstall an old system to have combined root+usr.
>>
>> I have always used an lvm installation guide that was a "companion"
>to
>> the handbook. That is it would tell you how to augment each handbook
>> installation chapter for lvm (actually lvm2).
>>
>> I can't find this documentation now on gentoo.org. There is a big
>wiki
>> page, but that is different as are daniel's 2-volume "learning linux
>> lvm".
>>
>> The closest I found is the raid+lvm quick install guide, but i would
>be
>> happier with the one I have used often in the past.
>>
>> Any clues (I am emotionally prepared to learn that it is right there
>on
>> the installation web page, but my eyes and search commands are
>> deficient).
>
>As James said, the docs are being reorganized. However, I did a
>systemd+LVM installation (just because I was getting tired of not
>knowing what the fuss was all about), and (in my experience) there are
>almost no changes from the regular installation in the handbook.
>
>I put everything in LVM (/, /boot, everything). From my notes, the
>only changes are:
>
>From the livecd:
>1. Use partitions, not whole disks (GRUB2 got confused when I tried to
>use whole disks).
>2. Set the partition type as LVM (8e in fdisk).
>3. Create the Physical Volume, the Volume Group, and the Logical
>Volumes as desired.
>4. Continue the normal installation, just using /dev/vg0/lvolX (or
>whatever names you choose).
>
>After the chroot and emerging the kernel package:
>1. Se the LVM options in the kernel. Compile, install it.
>2. Emerge systemd.
>3. Emerge dracut (USE="device-mapper", DRACUT_MODULES="systemd lvm", at
>least).
>4. Set add_dracutmodules="systemd" in /etc/dracut.conf.
>5. Weirdly, set lvmconf="no" in /etc/dracut.conf. I didn't even
>touched /etc/lvm/lvm.conf, so I think leaving it out makes dracut to
>autoconfigure it. If I put lvmconf="yes", the boot hangs. Didn't
>investigated why.
>6. Emerge GRUB2 (USE="device-mapper mount"); I don't know if GRUB
>works with LVM, but GRUB2 does, so I used that.
>7. Set GRUB_PRELOAD_MODULES="lvm",
>GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd", in
>/etc/default/grub.
>8. Generate initramfs, generate /boot/grub2/grub.cfg, install GRUB2
>with grub2-install.
>9. Reboot. Everything works.
>
>GRUB2 handles LVM just fine, I believe, but my LVM setup was dead
>simple (the VG was just the only partition of all my disks).
>dracut+systemd takes care of everything else; I didn't even had to do
>something special in fstab, since I used labels.
>
>To extend/reduce your Logical Volumes you will need a livecd, or a
>more complex initramfs, though.
>
>Regards.
Canek,
LVs can be resized while the system is running. It also depends on the actual filesystem, but extending can be done online with all filesystems I am aware of.
Shrinking is not possible with all.
--
Joost
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 3922 bytes --]
next prev parent reply other threads:[~2013-08-30 5:22 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 ` [gentoo-user] " Canek Peláez Valdés
2013-08-30 5:47 ` Alan McKinnon
2013-08-30 7:17 ` Dale
2013-08-30 5:21 ` J. Roeleveld [this message]
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=3d90a1d3-1a1e-4a4c-82b9-e0d34237c103@email.android.com \
--to=joost@antarean.org \
--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