From: Eric Levy <contact@ericlevy.name>
To: linux-btrfs@vger.kernel.org
Subject: Re: receive failing for incremental streams
Date: Wed, 15 Dec 2021 18:52:54 -0500 [thread overview]
Message-ID: <0735c9e2d4d6fa246965663a4f0d4f5211a5b8dc.camel@ericlevy.name> (raw)
In-Reply-To: <55ddb05b-04ad-172e-bda7-757db37a37b2@cobb.uk.net>
Thank you for the reply. Please see my questions, below.
On Wed, 2021-12-15 at 23:35 +0000, Graham Cobb wrote:
> There is no such thing as an incremental stream. Send sends all the
> information necessary to create a subvolume. Some of that includes
> instructions to share data in other subvolumes but it is not
> incremental.
Perhaps you would clarify the distinction, as to me an incremental
backup is a minimal set of data needed to recreate the original volume
when combined with the previous capture.
> You don't. Receive will create a new subvolume - which will include
> unchanged data from the initial stage and whatever changes have
> happened. If you want, you can then snapshot that (read-only or
> read-write as you wish) into any position you want in your
> destination
> filesystem.
How should I use the latter stream? From the stream length it is
obvious it does not contain most of the data from the earlier one.
next prev parent reply other threads:[~2021-12-15 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 20:27 receive failing for incremental streams Eric Levy
2021-12-15 23:35 ` Graham Cobb
2021-12-15 23:52 ` Eric Levy [this message]
2021-12-16 0:55 ` Graham Cobb
2021-12-16 1:13 ` Eric Levy
2021-12-16 10:24 ` Graham Cobb
2021-12-16 11:38 ` Hugo Mills
2021-12-18 23:53 ` Eric Levy
2021-12-16 5:36 ` 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=0735c9e2d4d6fa246965663a4f0d4f5211a5b8dc.camel@ericlevy.name \
--to=contact@ericlevy.name \
--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;
as well as URLs for NNTP newsgroup(s).