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: Fri, 04 Dec 2020 14:44:09 +0100 [thread overview]
Message-ID: <40b352dfa84e0f22d76e9b4f47111117549fa3bb.camel@gmx.net> (raw)
In-Reply-To: <CAL3q7H5AOeFit_kz4X9Q2hXqeHXxamQ+pm04yA5BqkYr3-5e+g@mail.gmail.com>
On Fri, 2020-12-04 at 10:22 +0000, Filipe Manana wrote:
> Ah, that's interesting.
>
> There are two different inodes with the same number (257) and
> different generations (359797 and 1571). Are you using, or ever used,
> in that filesystem the mount option "-o inode_cache" (it's deprecated
> for a while)?
No.
Which mount options do you need, the sending or the receiving btrfs?
My mount options on the receiving:
/dev/mapper/localdata_crypt on /mnt/autofs/local/data type btrfs (rw,noatime,nodiratime,compress-force=zstd:15,noacl,space_cache=v2,subvolid=5,subvol=/)
Maybe that space_cache=v2 is special.
> Even if not, it's still possible to get two different inodes with the
> same number, just not very common (specially with such a large
> difference in the generation numbers), and send is generally prepared
> to deal with such cases, just not this case, and I think I know why it
> happens. I'll have to see if I can reproduce it.
>
> If I send you a patch, are you able to patch the kernel, build it and test it?
Yes, I will try.
Best regards,
Massimo
next prev parent reply other threads:[~2020-12-04 13:50 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. [this message]
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.
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=40b352dfa84e0f22d76e9b4f47111117549fa3bb.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