From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "André Malm" <admin@sheepa.org>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs send with parent different size depending on source of files.
Date: Sat, 16 Feb 2019 23:32:53 +0300 [thread overview]
Message-ID: <bf5aa831-1501-2348-3542-aa388858be21@gmail.com> (raw)
In-Reply-To: <1cd9e028-931d-0ca3-8ece-710a039c552b@gmail.com>
16.02.2019 23:26, Andrei Borzenkov пишет:
...
>> Difference suggests the order does not matter. Increment suggests it
>> does matter.
>>
>> btrfs sub create A
>> cp somestuff A
>> btrfs sub snap -r A a.1
>> cp morestuff A
>> btrfs sub snap -r A a.2
>>
>> The normal case of send is:
>>
>> btrfs send -p a.1 a.2
>>
>> However, is it valid to do?
>>
>> btrfs send -p a.2 a1
>>
>
> Of course it is. Stream contains differences between the first and the
> second stream, where order does matter. "Incremental" implies temporal
> ordering between two snapshots which does not exist on "btrfs send"
> level and must be ensured by tools that use "btrfs send/receive". There
> is no inherent parent/child or temporal relationship implied by "btrfs
> send" itself. "btrfs send" *will* compute differences from a.1 to a.2
> although a.2 is newer than a.1; it is up to you to ensure you apply this
> stream to correct base on destination.
>
And BTW your example can actually be useful to revert (roll back)
content of volume to previous snapshot.
next prev parent reply other threads:[~2019-02-16 20:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 11:37 Btrfs send with parent different size depending on source of files André Malm
2019-02-14 22:37 ` Chris Murphy
2019-02-15 4:00 ` Remi Gauvin
2019-02-15 18:38 ` Chris Murphy
2019-02-15 18:56 ` Remi Gauvin
2019-02-16 20:10 ` Andrei Borzenkov
2019-02-15 17:45 ` Andrei Borzenkov
2019-02-15 19:11 ` Chris Murphy
2019-02-16 20:26 ` Andrei Borzenkov
2019-02-16 20:32 ` Andrei Borzenkov [this message]
2019-02-18 18:00 ` Chris Murphy
2019-02-15 19:29 ` Remi Gauvin
2019-02-15 19:41 ` Remi Gauvin
2019-02-16 20:08 ` Andrei Borzenkov
2019-02-17 3:11 ` Remi Gauvin
2019-02-18 13:05 ` André Malm
2019-02-18 18:06 ` Chris Murphy
2019-02-18 19:58 ` André Malm
2019-02-18 20:59 ` Graham Cobb
2019-02-18 21:22 ` Chris Murphy
2019-02-18 21:36 ` André Malm
2019-02-18 22:28 ` Chris Murphy
2019-02-18 22:58 ` André Malm
2019-02-18 23:49 ` Chris Murphy
2019-02-18 23:58 ` André Malm
2019-02-19 0:16 ` Chris Murphy
2019-02-19 0:17 ` Chris Murphy
2019-02-19 0:28 ` André Malm
2019-02-19 3:54 ` Chris Murphy
2019-02-19 12:05 ` André Malm
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=bf5aa831-1501-2348-3542-aa388858be21@gmail.com \
--to=arvidjaar@gmail.com \
--cc=admin@sheepa.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).