linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@windriver.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Any way to speed up activation of volumes with snapshots?
Date: Mon, 14 Sep 2015 12:05:12 -0600	[thread overview]
Message-ID: <55F70C58.5010205@windriver.com> (raw)

Hi,

I'm running a 3.10 kernel with LVM 2.02.95.

I'm running into a problem where activating snapshots can take quite a long 
time, roughly one minute per 25GB of delta between the snapshot and the origin 
volume.  (See below for my test procedure.)

I realize that my kernel/LVM aren't exactly bleeding edge, and I wondering 
whether more recent versions have done anything to speed up the activation 
process (like maybe making it more lazy-loaded rather than reading in a bunch of 
data up-front).

If anyone is aware of such improvements, I'd appreciate it if you could point me 
at the appropriate changes.


For those that are interested, the test that I did was as follows:

lvcreate -L100G  -n test1 vg
lvcreate -L 100G -s -n test1snapshot /dev/vg/test1
dd if=/dev/zero of=/dev/cinder-volumes/test1snapshot bs=1M count=95000
lvchange -an  /dev/cinder-volumes/test1snapshot
time lvchange -ay  /dev/cinder-volumes/test1snapshot

The final "lvchange" command took about 4m22s.  This works out to 362MB/sec, 
which is almost exactly the speed I got doing a "dd" from the volume to /dev/null.

Thanks,
Chris

             reply	other threads:[~2015-09-14 18:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 18:05 Chris Friesen [this message]
2015-09-14 18:46 ` [linux-lvm] Any way to speed up activation of volumes with snapshots? Chris Friesen
2015-09-14 18:47 ` Zdenek Kabelac
2015-09-14 19:16   ` Chris Friesen
2015-09-14 19:41     ` Zdenek Kabelac
2015-09-15  8:41     ` Zdenek Kabelac
2015-09-15 16:54       ` Chris Friesen
2015-09-15 23:03 ` Chris Friesen
2015-09-16  8:27   ` Zdenek Kabelac
2015-09-16 15:30     ` Chris Friesen
2015-09-16 21:21       ` Zdenek Kabelac
2015-09-16 19:19     ` Chris Friesen
2015-09-16 21:20       ` Zdenek Kabelac

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=55F70C58.5010205@windriver.com \
    --to=chris.friesen@windriver.com \
    --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).