From: Leonard Lausen <leonard@lausen.nl>
To: linux-btrfs@vger.kernel.org
Subject: btrfs send receive ERROR: chown failed: No such file or directory
Date: Fri, 21 Sep 2018 12:30:32 +0000 [thread overview]
Message-ID: <87a7obowwn.fsf@lausen.nl> (raw)
Hello!
I observe the following issue with btrfs send | btrfs receive in a setup
with 2 machines and 3 btrfs file-systems. All machines run Linux 4.18.9.
Machine 1 runs btrfs-progs 4.17.1, machine 2 runs btrfs-progs 4.17 (via
https://packages.debian.org/stretch-backports/btrfs-progs).
1) Machine 1 takes regular snapshots and sends them to machine 2. btrfs
btrfs send ... | ssh user@machine2 "btrfs receive /path1"
2) Machine 2 backups all subvolumes stored at /path1 to a second
independent btrfs filesystem. Let /path1/rootsnapshot be the first
snapshot stored at /path1 (ie. it has no Parent UUID). Let
/path1/incrementalsnapshot be a snapshot that has /path1/rootsnapshot
as a parent. Then
btrfs send -v /path1/rootsnapshot | btrfs receive /path2
works without issues, but
btrfs send -v -p /path1/rootsnapshot /path1/incrementalsnapshot | btrfs receive /path2
fails as follows:
ERROR: chown o257-4639416-0 failed: No such file or directory
No error is shown in dmesg. /path1 and /path2 denote two independent
btrfs filesystems.
Note that there was no issue with transferring incrementalsnapshot from
machine 1 to machine 2. No error is shown in dmesg.
Best regards
Leonard
next reply other threads:[~2018-09-21 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 12:30 Leonard Lausen [this message]
2018-10-02 6:00 ` btrfs send receive ERROR: chown failed: No such file or directory Leonard Lausen
2018-10-02 19:40 ` Filipe Manana
2018-10-11 11:36 ` Leonard Lausen
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=87a7obowwn.fsf@lausen.nl \
--to=leonard@lausen.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.