From: Randall Smith <randall@tnr.cc>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm partition on lv
Date: Mon, 07 Aug 2006 20:17:22 -0500 [thread overview]
Message-ID: <eb8oo1$rj2$1@sea.gmane.org> (raw)
Warning: This may be insane.
I like the flexibility of LVM and try to use it wherever it's feasible.
In this case, I'd like a Xen guest OS to have control over it's LV's.
The method I usually see for using LVM with Xen is to create an LV and
a filesystem on it. I would like to instead create an LV and partition
it with an LVM partition and maybe other partition types. Just to test
this I did the following:
1. lvcreate -L 100M -name test vg1
2. cfdisk /dev/vg1/test
3. create LVM partition on entire device
4. pvcreate /dev/vg1/test
5. vgcreate vg2 /dev/vg1/test
6. vgchange -ay /dev/vg2
7. lvcreate -L 50M -n testlv vg2
8. mkfs.ext3 /dev/vg2/testlv
9. mkdir /mnt/test
10. mount /dev/vg2/testlv /mnt/test
And it worked! Cool!
Let's say on /dev/vg1/test I had one LVM partition and one ext3
partition. How can I access those separate partitions since it's only
one device (/dev/vg1/test)? Normally, a partitioned block device
(/dev/hda) would show up like /dev/hda1, dev/hda2, etc.
In the example above, I'm partitioning the LV and using the partition on
the same system, which is useless. What I will be doing is giving the
disk image /dev/vg1/test to a Xen guest so it can have it's own VG and
LVs. Are there potential problems I should look out for and/or tweaking
I should do to make this work optimally?
Randall
next reply other threads:[~2006-08-08 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 1:17 Randall Smith [this message]
2006-08-08 10:34 ` [linux-lvm] lvm partition on lv Markus Laire
2006-08-08 10:40 ` Markus Laire
2006-08-08 14:27 ` [linux-lvm] " Randall Smith
2006-08-14 4:42 ` Randall Smith
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='eb8oo1$rj2$1@sea.gmane.org' \
--to=randall@tnr.cc \
--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 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 NNTP newsgroup(s).