From: Goffredo Baroncelli <kreijack@libero.it>
To: Alexander Block <ablock84@googlemail.com>
Cc: kreijack@inwind.it, linux-btrfs@vger.kernel.org
Subject: Re: [RFC] Btrfs "sendshots" and hidden snapshots
Date: Fri, 06 Jul 2012 14:00:46 +0200 [thread overview]
Message-ID: <4FF6D36E.7000201@libero.it> (raw)
In-Reply-To: <CAB9VWqBcZNc7unKA9sFC9nUrBgCB=G3tsDy89QXiQBmdvzbkwA@mail.gmail.com>
On 07/06/2012 10:51 AM, Alexander Block wrote:
> On Fri, Jul 6, 2012 at 12:34 AM, Goffredo Baroncelli <kreijack@libero.it> wrote:
>> On 07/05/2012 06:51 PM, Alexander Block wrote:
>>> Hello all,
>>>
[....]
>>> When we later do an incremental send we can do this:
>>> 1. Do the same as point 1. from above.
>>> 2. Determine which of the previous sendshots is the correct one for
>>> the incremental send. We could use some magic auto detection here or
>>> the user has to specify it by himself.
>>> 3. Use the hidden snapshot from 1. and the determined sendshot from 2.
>>> to find the incremental changes and do the send.
>>
>> I can understand how a sendshot could be used to compute the metadata
>> delta. But how compute the data delta ?
> We still would have the file extent data found in the metadata. When
> we see that logical addresses or generations have changed, we know the
> data has changed. This may however be problematic in case a defrag or
> balance was performed, for this we should probably introduce a data
> only transid or something like that which is preserved on such
> operations.
Yes, this makes sense. The data that has to be collected is only the new
one, if I can track which data is changed (comparing the extent data )
then I need only the new data.
>>
prev parent reply other threads:[~2012-07-06 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 16:51 [RFC] Btrfs "sendshots" and hidden snapshots Alexander Block
2012-07-05 22:34 ` Goffredo Baroncelli
2012-07-06 8:51 ` Alexander Block
2012-07-06 11:55 ` Chris Mason
2012-07-06 12:03 ` Goffredo Baroncelli
2012-07-06 12:45 ` Alexander Block
2012-07-09 15:51 ` Goffredo Baroncelli
2012-07-06 12:00 ` Goffredo Baroncelli [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=4FF6D36E.7000201@libero.it \
--to=kreijack@libero.it \
--cc=ablock84@googlemail.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
/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.