All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: giovanni_re <john_re@fastmail.us>
Subject: Re: [linux-lvm] Disk Partitioning tools, GUI preferably- best for LVM Logical Volume Management ; jor
Date: Mon, 26 Jul 2010 13:43:18 +0100	[thread overview]
Message-ID: <4C4D82E6.3080303@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1007260805250.3000@bmsred.bmsi.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/26/2010 01:16 PM, Stuart D. Gathman wrote:
> On Mon, 26 Jul 2010, Bryn M. Reeves wrote:
> 
>> On 07/24/2010 04:28 AM, giovanni_re wrote:
>>> So, I've got that big LV 4th partition, with empty space (2TB drive),
>>> and now I want to create some more linux partitions so I can install
>>> some other distros.
>>
>> If you want VMs then partitioning an LV makes sense. You present the
>> entire LV as a virtual disk to the guest and the emulated devices appear
>> to that OS as a regular partitioned disk. This is a very common technique.
> 
> Using Xen modified OSes, you don't need to partition the LVs.  The 
> xen storage driver presents each mapped block device as a virtual
> partition.

Not used Xen for a long time but that's good to know - iirc it did not
behave like this the last time I used it (with xvda disks).

> Booting multiple LVM supporting OSes works fine with LVM.  Have a LV for the
> root filesystem of each Linux OS, and have them all on the Grub menu.
> Make the /boot partition extra large.  I do this with every laptop
> and desktop as SOP.  Make Fedora upgrades much less fearful.

That's exactly what I was suggesting :-)

Adding nested partitions _inside_ the LVs (which is what the OP seemed
to want) is going to complicate things significantly for bare-metal.

> If every distro sticks to reasonable naming conventions in /boot (so
> that they don't step on each others kernels), then it all works fine.

Yes although you still need to be a little careful during installations
to make sure that there aren't any conflicts (I often want to have a
couple of versions of the same distribution, or even different instances
of the same version of the same distribution installed together). Also
remember never to re-format /boot during an install :)

Regards,
Bryn.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkxNguYACgkQ6YSQoMYUY97YHACfUlBWe2NnmC8ztIZ0ZGa46xKU
ByEAoIfCSb0XUzR+Usy5VE9SGq3AXl2U
=+GcI
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-07-26 12:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24  3:28 [linux-lvm] Disk Partitioning tools, GUI preferably- best for LVM Logical Volume Management ; jor giovanni_re
2010-07-24  4:39 ` Stuart D. Gathman
2010-07-24 16:54 ` Harald Heigl
2010-07-26  8:45 ` Bryn M. Reeves
2010-07-26 12:16   ` Stuart D. Gathman
2010-07-26 12:43     ` Bryn M. Reeves [this message]
2010-07-26 13:59       ` Stuart D. Gathman
2010-07-26 14:04         ` Bryn M. Reeves
2010-07-26 16:48           ` Stuart D. Gathman
2010-07-26 22:32   ` [linux-lvm] Disk Partitioning tools, - for having multi distros bootable - " giovanni_re
2010-07-28 18:10     ` Stuart D Gathman

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=4C4D82E6.3080303@redhat.com \
    --to=bmr@redhat.com \
    --cc=john_re@fastmail.us \
    --cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.