From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: back&forth send/receiving?
Date: Fri, 17 Feb 2023 20:25:30 +0300 [thread overview]
Message-ID: <c0e00d00-20ff-642f-bbfd-ecbd17669502@gmail.com> (raw)
In-Reply-To: <d02fb95aecf51439c7784c990784f73a11412e4b.camel@scientia.org>
On 17.02.2023 20:12, Christoph Anton Mitterer wrote:
> ~/mnt/master# btrfs send snap-1 | /usr/bin/time -v btrfs receive ~/mnt/copy1/
> ~/mnt/master# btrfs send snap-1 | /usr/bin/time -v btrfs receive ~/mnt/copy2/
> ~/mnt/master# btrfs subvolume snapshot -r data/ snap-2
> Create a readonly snapshot of 'data/' in './snap-2'
> ~/mnt/master# btrfs send -p snap-1 snap-2 | /usr/bin/time -v btrfs receive ~/mnt/copy1/
> ~/mnt/master# btrfs send -p snap-1 snap-2 | /usr/bin/time -v btrfs receive ~/mnt/copy2/
So copy1 and copy2 are identical. This is not what you said earlier (at
least, it is not how what you said earlier sounded).
Of course you can use either of them and continue incremental chain on
another.
...
>
> They may or may not be.
> Sometimes, I just send the same snapshot (e.g. from some specific date)
> to all copyN ... sometimes the most recent one of all of them is
> different.
>
So are all copyN identical or not?
> But I always keep on (old) master the snapshot that are most recent on
> each of copyN, so that I can continue from there, when I do the next
> round of snapshot.
>
It does not matter what you keep on old master because old master is
gone. What matter is what you keep on each copyN.
next prev parent reply other threads:[~2023-02-17 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 16:42 back&forth send/receiving? Christoph Anton Mitterer
2023-02-04 6:10 ` Andrei Borzenkov
2023-02-06 3:07 ` Christoph Anton Mitterer
2023-02-06 4:16 ` Andrei Borzenkov
2023-02-06 4:31 ` Christoph Anton Mitterer
2023-02-06 6:46 ` Andrei Borzenkov
2023-02-17 17:12 ` Christoph Anton Mitterer
2023-02-17 17:25 ` Andrei Borzenkov [this message]
2023-02-18 0:29 ` Christoph Anton Mitterer
2023-02-18 6:57 ` Andrei Borzenkov
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=c0e00d00-20ff-642f-bbfd-ecbd17669502@gmail.com \
--to=arvidjaar@gmail.com \
--cc=calestyo@scientia.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox