ssh other-server 'btrfs send -p /mnt/snaps/parent-subvol
subvol-to-send' | btrfs receive /mnt/my-backups/
Thanks. I was unable to reproduce the bug with a simple incremental
send like this between two Debian 12 (bookworm systems).
This is hard to reproduce, i have tried, but didn't suceed.
How can I reproduce these errors? Are you using sending or receiving
from within a container or flatpak?
Since October I didn't have any more issues — I don't know why.
System is exactly the same.
Maybe problem stopped after kennel upgrade, or btrfs-progs upgrade.
In a week or so I'll be able to backport btrfs-progs 6.12. If you
suspect a kernel or btrfs-progs bug you'll want to test those. Also,
you'll want to update the upstream forwarded bug with your results at
that time.
I will have to wait for new errors to emerge.
But current settings from debian stable don't show these errors since
October.
# dpkg -l | grep -E 'btrfs-progs|linux-image'; echo; uname -a
ii btrfs-progs 6.2-1+deb12u1 amd64
Checksumming Copy on Write Filesystem utilities
ii linux-image-6.1.0-25-amd64 6.1.106-3 amd64 Linux 6.1 for
64-bit PCs (signed)
ii linux-image-6.1.0-26-amd64 6.1.112-1 amd64 Linux 6.1 for
64-bit PCs (signed)
ii linux-image-6.1.0-27-amd64 6.1.115-1 amd64 Linux 6.1 for
64-bit PCs (signed)
ii linux-image-6.1.0-28-amd64 6.1.119-1 amd64 Linux 6.1 for
64-bit PCs (signed)
ii linux-image-amd64 6.1.119-1 amd64 Linux for
64-bit PCs (meta-package)
Linux zefir 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1
(2024-11-22) x86_64 GNU/Linux
Thanks. I'm still not able to reproduce. Can you think of anything
else? What happens when you do a full send (no parent, no incremental)?
So maybe we close this bug and reopen if I hit errors again?
I will write email to you when this happens again?
