From: Brian Neu <proclivity76@yahoo.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] snapshot pools, lvm roadmap
Date: Tue, 4 Jan 2011 23:11:16 -0800 (PST) [thread overview]
Message-ID: <581831.19828.qm@web39308.mail.mud.yahoo.com> (raw)
For many years, I've greatly desired a snapshotting solution which goes above
and beyond the current lvm features. I'd love to see the ability to instantiate
a storage pool for creating snapshots, with either a first-in-first-out or even
some other method for bumping snapshots when the pool fills up. The
inefficiency of the former style of lvm snapshots in both space and speed and
the cumbersome nature of managing them has kept me looking for alternatives.
Btrfs isn't quite there yet and may not be through 2011 or beyond. zfs-fuse
can't seem to act as a volume manager and I'm having problems with crashes.
Frustrated, I'm turning back to lvm.
So now I'm looking at the lvm wiki and I'm seeing "shared exception store".
Can someone fill me in on the current status of this effort as the wiki was
last updated in May-2009 ?
Thanks!
next reply other threads:[~2011-01-05 7:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 7:11 Brian Neu [this message]
2011-01-05 18:34 ` [linux-lvm] snapshot pools, lvm roadmap Brian Neu
2011-01-06 11:59 ` Joe Thornber
2011-01-07 19:33 ` Brian Neu
2011-01-07 20:27 ` Phillip Susi
2011-01-07 20:41 ` Alasdair G Kergon
2011-01-10 10:15 ` Joe Thornber
2011-01-10 15:30 ` Phillip Susi
2011-01-05 18:45 ` Stuart D. Gathman
2011-01-05 20:56 ` Brian Neu
2011-01-06 16:15 ` Phillip Susi
2011-01-07 1:09 ` Stuart D. Gathman
2011-01-07 19:01 ` Brian Neu
2011-01-08 16:17 ` Stuart D. Gathman
-- strict thread matches above, loose matches on Subject: below --
2011-01-18 15:39 Brian Neu
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=581831.19828.qm@web39308.mail.mud.yahoo.com \
--to=proclivity76@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.