From: A L <crimsoncottage@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Cerem Cem ASLAN <ceremcem@ceremcem.net>
Subject: Re: Btrfs incremental send | receive fails with Error: File not found
Date: Tue, 1 Aug 2017 22:33:06 +0200 [thread overview]
Message-ID: <dfe50824-e77a-d07b-e578-5a8d9e2c7478@gmail.com> (raw)
In-Reply-To: <CAN4oSBf1pGAS9e-SM_0NAA0jJthrOADOgapWRT+i3akWAO_h+w@mail.gmail.com>
On 8/1/2017 10:24 PM, Cerem Cem ASLAN wrote:
> What is that mean? Can't we replicate the same snapshot with `btrfs
> send | btrfs receive` multiple times, because it will have a "Received
> UUID" at the first `btrfs receive
You will need to make a new read-write snapshot of the received volume
to fix it. Any snapshots created from the received subvolume can't be
used for send-receive again, afaik.
# btrfs subvolume snapshot subvolume.received subvolume
next prev parent reply other threads:[~2017-08-01 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 17:26 Btrfs incremental send | receive fails with Error: File not found A L
2017-07-28 19:32 ` Hermann Schwärzler
2017-07-28 23:26 ` A L
2017-08-01 12:54 ` A L
2017-08-01 20:24 ` Cerem Cem ASLAN
2017-08-01 20:33 ` A L [this message]
2017-08-01 20:39 ` Cerem Cem ASLAN
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=dfe50824-e77a-d07b-e578-5a8d9e2c7478@gmail.com \
--to=crimsoncottage@gmail.com \
--cc=ceremcem@ceremcem.net \
--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).