From: Sampson Fung <sampsonfung@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send -c: ERROR: parent determination failed for 330
Date: Tue, 1 Jun 2021 15:18:32 +0800 [thread overview]
Message-ID: <CACEy+ETdogdch6VC9KijA7gfbgR0bCNG9mXfhwCuUkXQr=u1iQ@mail.gmail.com> (raw)
In-Reply-To: <CACEy+ETCvJ+cKn6N4maL0Dq1608pKtCXYSX6CO0oz4B8X1=gLw@mail.gmail.com>
Typos in 7 & 8. Should be:
7. send A10 over by trfs -p A0 A10
8. send B10 over by btrfs -c A0 B10, then error
On Tue, Jun 1, 2021 at 3:13 PM Sampson Fung <sampsonfung@gmail.com> wrote:
>
> My full test setup is post at
> https://ask.fedoraproject.org/t/can-i-continue-incremental-send-after-subvol-is-split/14597?u=sampsonf
>
> In short:
>
> 1. create a new subvol A
> 2. create 8 new files in A
> 3. create readonly snapshot as A0
> 4. send over by btrfs send /source/A0 | btrfs receive .
> 5. split A into two subvols A & B, and move 4 files over
> A/file1-file4
> A/B/file5-file8
> 6. create readonly snapshot. A as A10 & B as B10
> 7. send A10 over by btrfs -p A1 A10
> 8. send B10 over by btrfs -c A1 B10, then error
>
> Why was that? What is the most efficient way to send over B10?
prev parent reply other threads:[~2021-06-01 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 7:13 btrfs send -c: ERROR: parent determination failed for 330 Sampson Fung
2021-06-01 7:18 ` Sampson Fung [this message]
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='CACEy+ETdogdch6VC9KijA7gfbgR0bCNG9mXfhwCuUkXQr=u1iQ@mail.gmail.com' \
--to=sampsonfung@gmail.com \
--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).