From: "Stuart D. Gathman" <stuart@bmsi.com>
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 17:57:18 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1011151755270.4470@bmsred.bmsi.com> (raw)
In-Reply-To: <20101115203757.GA5876@yahoo.fr>
On Mon, 15 Nov 2010, Stephane Chazelas wrote:
> ddsnap (zumastor) worked great but is no longer maintained.
>
> - LVM snapshots: poor performace or very few snapshots
> - ddsnap: got to stick with an old kernel
zumastor doesn't depend on kernel versions - it uses device-mapper just
like regular snapshots. (Or does it have a special device-mapper
kernel module?)
> - btrfs, not really production ready yet. Probably your best bet
> though.
This is good too, but at a different level. We still need LV snapshot.
> - fuse solutions, with all the fuse related issues.
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
prev parent reply other threads:[~2010-11-15 22:57 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
2010-11-15 22:57 ` Stuart D. 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=Pine.LNX.4.64.1011151755270.4470@bmsred.bmsi.com \
--to=stuart@bmsi.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).