From: Stuart Gathman <stuart@gathman.org>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] convert LV to physical device _in_place_?
Date: Thu, 13 Jul 2017 23:41:12 -0400 [thread overview]
Message-ID: <b5832376-fc6b-d24c-56fc-cac0bf8f00fa@gathman.org> (raw)
In-Reply-To: <55f9c8eb-41df-8b3b-c790-e81fbcef0a73@meduniwien.ac.at>
On 07/13/2017 09:25 AM, Matthias Leopold wrote:
> i'm fiddling around with LVM backed KVM raw disks, that i want to use
> _directly_ in oVirt virtualization (as "Direct LUN"). i would like to
> avoid "importing", dd, etc. if possible. in the KVM origin system
> exists a mapping of one iSCSI whole device (no partitions) to one PV
> to one VG to one LV per KVM disk. i can now present these iSCSI
> devices to the oVirt hosts, where i can only use them as "Direct LUN"
> without the LVM layer (i guess). so all i would need is to remove the
> LVM metadata from the iSCSI device preserving the "content" of the LV.
> pvremove seems to be too "intrusive" for this... i know this sounds
> rather naive and i didn't find any recipes for it. everybody talks
> about dd to a new device, which of course works (i tried it), but is
> exactly what i want to avoid when migrating very large disks (TB). i
> hope someone understands my concern and maybe has a solution
I use iSCSI at home, and I just export the LV as an iSCSI target. Now
you have direct LUN for use with VM hosts on the network (I just have a
gigabit LAN at home). The iSCSI server still uses LVM, and you can
snapshot the volume for backup on the server.
Maybe that's too obvious, and I misunderstood your problem?
There is no LVM metatdata on the exported iSCSI devices - that is on the
underlying disk. As the export LUN looks like a disk, you can even add
an optional partition table, PVs, VGs, etc for use by the virtual machine.
prev parent reply other threads:[~2017-07-14 3:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 13:25 [linux-lvm] convert LV to physical device _in_place_? Matthias Leopold
2017-07-13 15:25 ` Zdenek Kabelac
2017-07-13 16:06 ` Stuart D. Gathman
2017-07-13 19:54 ` Matthias Leopold
2017-07-13 20:05 ` Marek Podmaka
2017-07-14 3:41 ` Stuart Gathman [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5832376-fc6b-d24c-56fc-cac0bf8f00fa@gathman.org \
--to=stuart@gathman.org \
--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).