From: Eric Brunson <brunson@brunson.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshot rollback
Date: Wed, 24 Feb 2010 15:46:09 -0700 [thread overview]
Message-ID: <4B85AC31.8010508@brunson.com> (raw)
In-Reply-To: <20090923214034.GE3866@agk-dp.fab.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
On 09/23/2009 03:40 PM, Alasdair G Kergon wrote:
> On Wed, Sep 23, 2009 at 03:04:22PM -0600, Eric Brunson wrote:
>
>> I remember seeing somewhere discussion of adding the ability to roll
>> back to a snapshot. I think of how cool this would be about ever six
>> months, usually coinciding with an impending Fedora release. ;-)
>>
> The developers are just starting to submit their patch sequence to the
> development mailing lists (dm-devel and lvm-devel) for review. So
> that's targetting linux-next in the next few weeks ready for the 2.6.33
> kernel.
>
>
From the newly released 2.6.33 kernel changelog, does this mean what I
think it means?
commit 53365383c4667aba55385cd1858582c19a7a8a36
Merge: 51b736b d2fdb77
Author: Linus Torvalds<torvalds@linux-foundation.org>
Date: Tue Dec 15 09:12:01 2009 -0800
Merge git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-2.6-dm
* git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-2.6-dm: (80 commits)
dm snapshot: use merge origin if snapshot invalid
dm snapshot: report merge failure in status
dm snapshot: merge consecutive chunks together
dm snapshot: trigger exceptions in remaining snapshots during merge
dm snapshot: delay merging a chunk until writes to it complete
dm snapshot: queue writes to chunks being merged
dm snapshot: add merging
dm snapshot: permit only one merge at once
dm snapshot: support barriers in snapshot merge target
dm snapshot: avoid allocating exceptions in merge
dm snapshot: rework writing to origin
dm snapshot: add merge target
dm exception store: add merge specific methods
dm snapshot: create function for chunk_is_tracked wait
dm snapshot: make bio optional in __origin_write
...
If it does, then I'm very excited. :-)
e.
[-- Attachment #2: Type: text/html, Size: 2435 bytes --]
next prev parent reply other threads:[~2010-02-24 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 21:04 [linux-lvm] Snapshot rollback Eric Brunson
2009-09-23 21:29 ` Brian J. Murrell
2009-09-23 21:48 ` Eric Brunson
2009-09-23 21:40 ` Alasdair G Kergon
2009-09-23 21:47 ` Eric Brunson
2010-02-24 22:46 ` Eric Brunson [this message]
2010-02-25 0:09 ` Mike Snitzer
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=4B85AC31.8010508@brunson.com \
--to=brunson@brunson.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.