From: "Massimo B." <massimo.b@gmx.net>
To: fdmanana@gmail.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send -p failing: chown o257-1571-0 failed: No such file or directory
Date: Sun, 13 Dec 2020 10:50:28 +0100 [thread overview]
Message-ID: <c0aa48c7db8c00efe8dd9a2c72c425ffe57df49c.camel@gmx.net> (raw)
In-Reply-To: <CAL3q7H4r-EtnMc=VD2EP01HsLCqg-z8LfMnFseHrNEv=rjPT_g@mail.gmail.com>
On Wed, 2020-12-09 at 10:29 +0000, Filipe Manana wrote:
> So to confirm if there are other problems, you really need to let send
>
> and receive processes finish (don't kill them). If they finish without
>
> failure, then check if temporary directories (or files with the same
>
> name pattern) still exist or not.
I continued with send|receive successfully with a lot of snapshots, then I found
some new error. Is this also related?
clone mb/Documents.AZ/0.SYNC/....pdf - source=mb/Documents.AZ/0.SYNC/....pdf source offset=20705280 offset=20709376 length=4096
clone mb/Documents.AZ/0.SYNC/....pdf - source=mb/Documents.AZ/0.SYNC/....pdf source offset=20713472 offset=20713472 length=4096
ERROR: failed to clone extents to mb/Documents.AZ/0.SYNC/....pdf: Invalid argument
Best regards,
Massimo
next prev parent reply other threads:[~2020-12-13 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 10:18 btrfs send -p failing: chown o257-1571-0 failed: No such file or directory Massimo B.
2020-12-02 11:04 ` Filipe Manana
2020-12-04 7:21 ` Massimo B.
2020-12-04 10:22 ` Filipe Manana
2020-12-04 13:44 ` Massimo B.
2020-12-04 15:00 ` Filipe Manana
2020-12-09 10:05 ` Massimo B.
2020-12-09 10:29 ` Filipe Manana
2020-12-10 6:18 ` Massimo B.
2020-12-10 10:09 ` Filipe Manana
2020-12-13 9:50 ` Massimo B. [this message]
2020-12-14 9:46 ` Filipe Manana
2020-12-18 7:20 ` Massimo B.
2020-12-18 11:44 ` Filipe Manana
2021-01-11 11:49 ` Filipe Manana
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=c0aa48c7db8c00efe8dd9a2c72c425ffe57df49c.camel@gmx.net \
--to=massimo.b@gmx.net \
--cc=fdmanana@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