[linux-lvm] access or interface to list of blocks that have, changed via C.O.W.?
markw at mohawksoft.com
Fri Oct 5 11:21:16 UTC 2012
On 10/05/2012 05:26 AM, Bryn M. Reeves wrote:
> On 10/04/2012 04:02 PM, Mark Woodward wrote:
>> On 10/04/2012 10:44 AM, Bryn M. Reeves wrote:
>>> Really? I'd be surprised if it even builds against modern kernels or
>> 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
> Yes; that's the traditional dm-snapshot target that has been in the
> kernel for years. The Zumastor/ddsnap stuff was a separate project to
> replace that using a new metadata format and target - they are not the
> same and the Zumastor snapshot code was never merged in the kernel.
So, after this discussion, I went to my Ubuntu 12.04 system (3.2.0) and
tried some of my LVM2 utilities, and they read the header but found no
changes in a snapshot when clearly there had been some.
It seems I am wrong, but I'm a little confused, did the developers
change the format of the snapshot data COW file without changing the
file header signature? If so, that is very bad thing to do. If the COW
format has changed and the device header signature has not, how does one
correctly determine how the data is stored?
>>> Snapshots using the thinp target use the metadata format described in
>> Where are these files to be found?
> In drivers/md in the kernel sources - the dm-thin stuff was merged after
> 3.1 (October last year); see commits starting with 991d9fa.
More information about the linux-lvm