Linux LVM users
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: linux-lvm@redhat.com
Cc: Alasdair G Kergon <agk@redhat.com>, Milan Broz <mbroz@redhat.com>
Subject: [linux-lvm] ANNOUNCE: an experimental implementation of snapshot merging
Date: Tue, 3 Jun 2008 15:26:41 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806031516380.20514@engineering.redhat.com> (raw)

Hi

Here I release the first experimental implementation of snapshot merging. 
Merging allows you to copy data in snapshot back to the origin device. 
Once merging starts, it runs on background. When the merging finishes (you 
see "0%" with "lvs" command), you should remove the merging snapshot with 
lvremove command.

The userspace will still be changed, the kernel is already finished (there 
are no known bugs in the kernel, I'm curious about the unknown ones :)

Merging is initiated with "lvconvert -M vg/lv_snapshot" command. When you 
initiate merging, make sure that the origin device is not mounted. 
Snapshot can be mounted while it's merging is initiated.

During merging, aby reads and writes to the origin device are identical to 
accesses to the merging snapshots.

There may be multiple snapshots while one of them is being merged --- 
exceptions in other snapshots are being allocated and there snapshots are 
kept stable.

Don't try to concurrently merge more than one snapshot (the kernel refuses 
to do it, the userspace tools don't know about it --- the userspace will 
be rewritten anyway).

The patches are at:
http://people.redhat.com/mpatocka/patches/
The patches are for 2.6.26-rc4

(besides merging, there are some other bugfixes, I made for the kernel)

Mikulas

             reply	other threads:[~2008-06-03 19:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 19:26 Mikulas Patocka [this message]
2008-06-03 20:32 ` [linux-lvm] ANNOUNCE: an experimental implementation of snapshot merging Brian J. Murrell
2008-06-04 11:07   ` Mikulas Patocka
2008-06-04 14:07     ` Brian J. Murrell
2008-06-05 15:09       ` Mikulas Patocka
2008-06-03 20:43 ` Chris Cox
2008-06-03 20:51   ` Stuart D. Gathman
2008-06-03 23:38   ` Brian J. Murrell
2008-06-04  0:05     ` Chris Cox
2008-06-04  0:20       ` Greg Freemyer
2008-06-04  2:57         ` Brian J. Murrell
2008-06-04  3:23           ` Stuart D. Gathman
2008-06-04 11:11           ` Mikulas Patocka
2008-06-04 10:56   ` Mikulas Patocka
2008-06-04 14:01 ` Steeve McCauley
2008-06-05 15:01   ` Mikulas Patocka

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.0806031516380.20514@engineering.redhat.com \
    --to=mpatocka@redhat.com \
    --cc=agk@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=mbroz@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