From: Zdenek Kabelac <zkabelac@redhat.com>
To: markw@mohawksoft.com
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshots of snapshots are not supported yet
Date: Wed, 10 Jul 2013 22:15:17 +0200 [thread overview]
Message-ID: <51DDC0D5.2090900@redhat.com> (raw)
In-Reply-To: <d35fdbd25cedbfa7708394e716a3e288.squirrel@mail.mohawksoft.com>
Dne 10.7.2013 22:12, markw@mohawksoft.com napsal(a):
>> Dne 10.7.2013 16:45, markw@mohawksoft.com napsal(a):
>
>> As I said - btrfs has some kind of functionality you are looking for,
>> Or you may start to help with lvm project...
>> (Or thin-provisioning tools in this case)
>>
>> Zdenek
>
> That link you sent was good, I am looking in to it, it may provide a large
> amount of help.
>
> One last thing.... :-)
>
> Now imagine this:
>
> create disk0
>
> Activity on disk0
>
> Take a snapshot
> disk0 -> disk0_snap0
>
> Activity on disk0
>
> take a snapshot
> disk0 -> disk0_snap1
>
> (We will now use the differential between snap1 and snap0 to represent
> what needs to be backed up from snap1)
>
> This leaves us with something that looks like this:
>
> disk0 --> disk0_snap0
> -> disk0_snap1
>
> Will we need to remap the parentage of disk0_snap0 so it looks something
> like this?
>
> disk0 -> disk0_snap1 -> disk0_snap0
> (Is this possible with dmsetup?)
>
> Or could we have many (order of hundreds or thousands) of snaps directly
> on disk0 and not impact performance?
>
Thin provisioning is written to support this. Note - you do not need to have
snapshots present as active devices - i.e. you could snapshot your device
every hour.
If you want to discover diff between _snap0 and _snap1 - you have number of
choices - if you want to know 'filesystem' diff or block device diff.
Block device diff could be detected by doing a diff in metadata between
btree for _snap0 and _snap1.
Also there are projects like 'snapper' for filesystem diffs.
Zdenek
prev parent reply other threads:[~2013-07-10 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 16:05 [linux-lvm] Snapshots of snapshots are not supported yet markw
2013-07-08 17:41 ` Zdenek Kabelac
2013-07-08 17:57 ` markw
2013-07-08 19:03 ` Zdenek Kabelac
2013-07-10 3:45 ` markw
2013-07-10 8:25 ` Zdenek Kabelac
2013-07-10 14:45 ` markw
2013-07-10 18:43 ` Zdenek Kabelac
2013-07-10 19:16 ` markw
2013-07-10 20:12 ` markw
2013-07-10 20:15 ` Zdenek Kabelac [this message]
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=51DDC0D5.2090900@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=markw@mohawksoft.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).