From: Stuart D Gathman <stuart@bmsi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] access or interface to list of blocks that have, changed via C.O.W.?
Date: Thu, 04 Oct 2012 18:00:33 -0400 [thread overview]
Message-ID: <506E0701.1070103@bmsi.com> (raw)
In-Reply-To: <506DA504.8010509@mohawksoft.com>
On 10/04/2012 11:02 AM, Mark Woodward expounded in part:
>
>> snapshot target and metadata format. It does not share code with
>> current (or historic afaik) LVM2/device-mapper and has been dead for a
>> number of years (last commits around 2008).
>>
>>> get the code. It old and not supported currently, but still works.
>>> I
>> Really? I'd be surprised if it even builds against modern kernels or
>> device-mapper.
> ddsnap was the Zumastor snapshot tool which uses a different in-kernel
> Well.....
> The LVM2 code that ships with most distros still uses the old
> interfaces and still (Ubuntu 12.04) seemst to create a COW file with SnAp
This utility (ddsnap work alike) requires no kernel changes, and only
depends on the layout of the COW (and only on the changed block table):
http://www.opensvc.com/init/default/doc_storage_dds
next prev parent reply other threads:[~2012-10-05 0:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.18903.1349274978.3548.linux-lvm@redhat.com>
2012-10-03 15:42 ` [linux-lvm] access or interface to list of blocks that have, changed via C.O.W.? Mark Woodward
2012-10-04 2:52 ` Linda Walsh
2012-10-04 3:41 ` Mark Woodward
2012-10-04 5:05 ` Linda Walsh
2012-10-04 10:17 ` Mark Woodward
2012-10-04 14:44 ` Bryn M. Reeves
2012-10-04 15:02 ` Mark Woodward
2012-10-04 22:00 ` Stuart D Gathman [this message]
2012-10-05 9:39 ` Bryn M. Reeves
2012-10-05 9:26 ` Bryn M. Reeves
2012-10-05 11:21 ` Mark Woodward
2012-10-16 12:15 ` Mark Woodward
2012-10-17 10:20 ` Lars Ellenberg
2012-09-28 2:51 [linux-lvm] access or interface to list of blocks that have " Linda Walsh
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=506E0701.1070103@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 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.