From: Christoph Hellwig <hch@infradead.org>
To: J??rgen Gro?? <jgross@suse.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [RFC] Enhancement of loop driver?
Date: Fri, 13 Nov 2020 08:44:19 +0000 [thread overview]
Message-ID: <20201113084419.GA32694@infradead.org> (raw)
In-Reply-To: <1a5ccfd6-d7c1-28d5-3562-05178f44ed3d@suse.com>
On Fri, Nov 13, 2020 at 07:59:23AM +0100, J??rgen Gro?? wrote:
> a large customer is asking for storage migration of the disk images of
> their virtual machines. They don't want to migrate the VM to another
> host, but only the disk image from one filer to another while the VM
> keeps running.
>
> The natural way to setup something like this would be LVM and use
> mirroring, but the problem is that this requires to copy the image to
> a LVM enabled disk first, and this is no option due to time constraints
> (copying many GB of data takes too long, and in the end I'd like to be
> able to do the switch from the original image to the LVM backed with
> the VM kept running).
>
> So my idea was to enhance the loop driver to be capable to support a
> list of backing files instead of only one and use a small prepended
> file for storing the needed LVM metadata, resulting in the ability to
> keep the existing disk image.
>
> Would such an addition be acceptable?
Just use device mapper on top of the loop device, no need for changes
to the loop driver itself. Also qemu has some interesting migration
features that you might want to look into as they might suit you.
next prev parent reply other threads:[~2020-11-13 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 6:59 [RFC] Enhancement of loop driver? Jürgen Groß
2020-11-13 8:44 ` Christoph Hellwig [this message]
2020-11-13 8:59 ` Jürgen Groß
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=20201113084419.GA32694@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=jgross@suse.com \
--cc=linux-block@vger.kernel.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