From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] collapse (merge) snapshot into origin
Date: Thu, 6 Sep 2007 20:09:02 +0100 [thread overview]
Message-ID: <20070906190902.GX2064@agk.fab.redhat.com> (raw)
In-Reply-To: <1189098830.21669.47.camel@pc.ilinx>
On Thu, Sep 06, 2007 at 01:13:50PM -0400, Brian J. Murrell wrote:
> On Thu, 2007-09-06 at 13:06 -0400, Brian J. Murrell wrote:
> > [is] such a feature is
> > being considered for an official LVM release?
Snapshot merging: yes.
The patches depended on another change (tracking all snapshot I/O to eliminate
theoretical races) that's still outstanding, but once that's dealt with (it's
tricky - my original proof-of-concept patch was ~800 lines so needed breaking
up and rewriting), I expect them to follow quite quickly.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2007-09-06 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 17:06 [linux-lvm] collapse (merge) snapshot into origin Brian J. Murrell
2007-09-06 17:13 ` Brian J. Murrell
2007-09-06 19:09 ` Alasdair G Kergon [this message]
2009-09-23 22:20 ` [linux-lvm] " Brian J. Murrell
2009-09-23 22:39 ` Alasdair G Kergon
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=20070906190902.GX2064@agk.fab.redhat.com \
--to=agk@redhat.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).