Hello, does anyone have an idea about below issue? It is a severe issue as it renders btrfs send / receive dysfunctional and it is not clear if there may be a data corruption issue hiding in the current send / receive code. Thank you. Best regards Leonard Leonard Lausen <leonard@xxxxxxxxx> writes: > 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
