From: Douglas Paul <doug@bogon.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Eric Toombs <ewtoombs@uwaterloo.ca>
Subject: Re: [linux-lvm] faster snapshot creation?
Date: Wed, 26 Feb 2020 09:03:16 -0500 [thread overview]
Message-ID: <20200226140316.GA231654@bogon.ca> (raw)
In-Reply-To: <a4708de8-93f9-e663-3184-099a8e40ac3c@redhat.com>
On Wed, Feb 26, 2020 at 11:01:26AM +0100, Zdenek Kabelac wrote:
> If you are aspiring of creating tens of snapshot per second - you probably
> have very unusual workflow/requirement and mostly likely lvm2 is not the right
> tool for such task ATM.
> [...]
> So my advice - if you really need to use and create old snaps in very fast way
> is to developed your very own tool working in you restricted environment where
> you might probably not care about meta/data consistencies, deal with speed of
> udev and gazillion other issues - you can run your small 'ioctl()' stream much
> more efficiently.
For this workflow, it seems that using qemu-img in conjunction with
qemu-nbd might be a good option.
In this case, you build your reference image in a qcow image (as might
be used for a VM). For a test, you then create a temporary image based
on this reference image (using it as a backing file). Then you can mount
this new image using qemu-nbd to get a block device for it, and mount
the filesystem.
After your test is done, you can unmount, delete the nbd mapping, and
simply delete the temporary image you created.
It should be quite fast and lightweight. You should even be able to run
multiple tests in parallel.
--
Douglas Paul
next prev parent reply other threads:[~2020-02-26 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 11:58 [linux-lvm] faster snapshot creation? Eric Toombs
2020-02-25 9:31 ` Gionatan Danti
2020-02-25 9:38 ` Zdenek Kabelac
2020-02-25 21:35 ` Eric Toombs
2020-02-26 10:01 ` Zdenek Kabelac
2020-02-26 14:03 ` Douglas Paul [this message]
2020-02-26 0:38 ` 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=20200226140316.GA231654@bogon.ca \
--to=doug@bogon.ca \
--cc=ewtoombs@uwaterloo.ca \
--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).