From: Eric Levy <contact@ericlevy.name>
To: linux-btrfs@vger.kernel.org
Subject: Re: receive failing for incremental streams
Date: Wed, 15 Dec 2021 20:13:08 -0500 [thread overview]
Message-ID: <70553d13e265a2c7bced888f1a3d3b3e65539ce1.camel@ericlevy.name> (raw)
In-Reply-To: <ea6260d5-c383-9079-8a53-2051972b11d3@cobb.uk.net>
> Later you snapshot /data again to create /data-2 on the source
> system.
> You btrfs-send /data-2 to the other system again and it creates a new
> read-only subvolume - you tell btrfs-receive what to call it and
> where
> to put it, let's say you call it /copy-data-2 - using the data in the
> stream and reusing some extents from the existing /copy-data-1.
> /copy-data-2 is now a (read-only) copy of /data-2 from the source
> system.
>
> How you use that copy is up to you. If you are just taking backups
> you
> probably do nothing with it unless you have a problem (it will form
> part
> of the source for data for any future /copy-data-3). If you want to
> use
> it to initialize a read-write subvolume on the destination system you
> can take a read-write snapshot of /copy-data-2 to create a new
> subvolume
> (say /my-new-data) on the destination system.
Such is close to what I have always understood about receive, but the
confusion is that the second receive command makes no reference to the
subvolume created by the first command. How do I ultimately create a
restore target that combines the original full capture with the
incremental differences?
When I ask how I use it, I mean what commands do I enter into the
system.
Note in my case I archive the streams into regular (compressed) filesm
for later recovery.
next prev parent reply other threads:[~2021-12-16 1:13 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
2021-12-16 0:55 ` Graham Cobb
2021-12-16 1:13 ` Eric Levy [this message]
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=70553d13e265a2c7bced888f1a3d3b3e65539ce1.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).