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: Wed, 09 Dec 2020 11:05:14 +0100 [thread overview]
Message-ID: <1f78cd5d635b360e03468740608f3b02aea76b5d.camel@gmx.net> (raw)
In-Reply-To: <CAL3q7H7oLWGWJcg0Gfa+RKRGNf+d4mv0R9FQi2j=xLL1RNPTGA@mail.gmail.com>
On Fri, 2020-12-04 at 15:00 +0000, Filipe Manana wrote:
> Great, try this patch then: https://pastebin.com/raw/8NcPVUb0
>
>
>
> I haven't had the time yet to craft a reproducer and confirm that is
>
> the case you are running into, but from the receive -vvv output you
>
> provided before, it seems clear what the problem is.
No, that is not working.
It does not fail anymore and looks like transferring as expected. But the
receiving subvolume is exploding and creating lots of sub directories. I killed
the send|receive processes.
du is far bigger than the origin subvolume and reveals some of those subdirs:
~ du -sh /mnt/local/data/snapshots/root/root.20180114T131123+0100/
du: cannot access '/mnt/local/data/snapshots/root/root.20180114T131123+0100/o1568-359797-0': No such file or directory
du: cannot access '/mnt/local/data/snapshots/root/root.20180114T131123+0100/o6060-359797-0': No such file or directory
du: cannot access '/mnt/local/data/snapshots/root/root.20180114T131123+0100/o9279-359797-0': No such file or directory
du: cannot access '/mnt/local/data/snapshots/root/root.20180114T131123+0100/o19075-359797-0': No such file or directory
du: cannot access '/mnt/local/data/snapshots/root/root.20180114T131123+0100/o19076-359797-0': No such file or directory
...
du: cannot access '/mnt/local/data/snapshots/root/root.20180114T131123+0100/o65078-359798-0': No such file or directory
du: cannot access '/mnt/local/data/snapshots/root/root.20180114T131123+0100/o65084-359798-0': No such file or directory
du: cannot access '/mnt/local/data/snapshots/root/root.20180114T131123+0100/o65095-359798-0': No such file or directory
22G /mnt/local/data/snapshots/root/root.20180114T131123+0100/
compsize also reports about 20G referenced data.
The origin subvol has only 12G referenced.
Best regards,
Massimo
next prev parent reply other threads:[~2020-12-09 10:12 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. [this message]
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.
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=1f78cd5d635b360e03468740608f3b02aea76b5d.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