linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Stephane Chazelas <stephane_chazelas@yahoo.fr>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] advice for curing terrible snapshot performance?
Date: Mon, 15 Nov 2010 20:37:57 +0000	[thread overview]
Message-ID: <20101115203757.GA5876@yahoo.fr> (raw)
In-Reply-To: <AANLkTi=+iwZLBxZFzhb++KMevOy55QJrg9xg9Ey2w_kX@mail.gmail.com>

2010-11-12 13:52:25 -0800, chris (fool) mccraw:
[...]
> no snapshot  = ~11sec (727MB/sec)
> 1 snapshot   = ~102sec (78MB/sec)
> 2 snapshots  = ~144sec (55MB/sec)
> 3 snapshots  = ~313sec (25MB/sec)
> 4 snapshots  = ~607sec (15MB/sec)
[...]

Yes, from 2 snapshots on a volume LVM snapshots become unusable.
Other issues you may have with LVM snapshots with different
versions: some grub versions failing to see LVM volumes once
they have a snapshot, activating a volume group taking several
minutes when there are quite filled up volumes.

ddsnap (zumastor) worked great but is no longer maintained.

So, you have:

- LVM snapshots: poor performace or very few snapshots
- ddsnap: got to stick with an old kernel
- btrfs, not really production ready yet. Probably your best bet
though.
- fuse solutions, with all the fuse related issues.

Quite frustrating as the technolgy is here and has been around
for years.

Sorry for not bringing any good news. I'm all ears for good
alternative solutions though.

Another solution I had looked at at some point:

- qemu-nbd with qcow2: performance not there and a few issues as
well.

-- 
Stephane

  parent reply	other threads:[~2010-11-15 20:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 21:52 [linux-lvm] advice for curing terrible snapshot performance? chris (fool) mccraw
2010-11-12 22:28 ` Joe Pruett
2010-11-12 23:30   ` chris (fool) mccraw
2010-11-12 23:36   ` Joe Pruett
2010-11-13  0:17     ` chris (fool) mccraw
2010-11-13  0:58       ` Stuart D Gathman
2010-11-15 17:52         ` chris (fool) mccraw
2010-11-15 18:04           ` Romeo Theriault
2010-11-15 18:08           ` Joe Pruett
2010-11-15 18:18             ` chris (fool) mccraw
2010-11-15 23:51           ` Stuart D. Gathman
2010-11-16  0:09             ` chris (fool) mccraw
2010-11-15 18:05       ` chris (fool) mccraw
2010-11-15 14:35 ` Romeo Theriault
2010-11-15 17:46   ` chris (fool) mccraw
2010-11-15 20:37 ` Stephane Chazelas [this message]
2010-11-15 22:57   ` 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=20101115203757.GA5876@yahoo.fr \
    --to=stephane_chazelas@yahoo.fr \
    --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).