linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 08:21:37 +0100	[thread overview]
Message-ID: <d4891e0c7aa79895d8f85601954c7eb379b733fc.camel@gmx.net> (raw)
In-Reply-To: <CAL3q7H72N5q6ROhfvuaNNfUvQTe-mtHJVvZaS25oTycJ=3Um3w@mail.gmail.com>

On Wed, 2020-12-02 at 11:04 +0000, Filipe Manana wrote:

> Yes, it's a btrfs issue.

Thanks.
The bug report on btrbk side is:
https://github.com/digint/btrbk/issues/295

> There were two such bug fixes in 5.9 that are not included in a
> vanilla 5.8.15 (dunno if gentoo picked them into their 5.8.15 kernel):

I just switched to the most 5.9.12-gentoo and it's still the same issue.

> If those don't solve your problem. then the output of 'btrfs receive
> -vvv ...' could be used to help debug the issue.

# btrfs send -p /mnt/usb/mobiledata/snapshots/mobalindesk/root/root.20200803T060030+0200 /mnt/usb/mobiledata/snapshots/mobalindesk/root/root.20180114T131123+0100 | mbuffer -v 1 -q -m 2% | btrfs receive -vvv /mnt/local/data/snapshots/root/
At subvol /mnt/usb/mobiledata/snapshots/mobalindesk/root/root.20180114T131123+0100
At snapshot root.20180114T131123+0100
receiving snapshot root.20180114T131123+0100 uuid=dfd895bb-8f3e-ae46-82a5-21e22453a258, ctransid=542345 parent_uuid=95819f51-40a4-9745-9661-7871dce44e19, parent_ctransid=542414
utimes
rename home -> o257-359797-0
mkdir o257-1571-0
rename o257-1571-0 -> .hg
utimes
chown o257-1571-0 - uid=0, gid=0
ERROR: chown o257-1571-0 failed: No such file or directory


Best regards,
Massimo


  reply	other threads:[~2020-12-04  7:24 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. [this message]
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.
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=d4891e0c7aa79895d8f85601954c7eb379b733fc.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;
as well as URLs for NNTP newsgroup(s).