1. Are you piping the send stream to another system, and receiving it
there?
Yes.
This is something like this:
ssh other-server 'btrfs send -p /mnt/snaps/parent-subvol
subvol-to-send' | btrfs receive /mnt/my-backups/
2. What is special about ZK_83308/Documents/fk-2228.jpg ? Apparmor
won't do anything with it, your steps to reproduce (and others at all
provided links) don't appear to explain what's happening with this
file... Do you use selinux or tomoyo on the sender or receiver system?
I don't use selinux.
I tried to figure out what's special about files but I didn't find any
clue.
Files are different...
Last errors of this type I have seen in October:
lremovexattr
root/Omega/Domains/Oferty/Folders/OF_81080/Documents/81080_czok_Klucz.pdf
security.capability failed: No data available
lremovexattr
root/Omega/Domains/Produkty_Typowe/Folders/Lustro_Joy_50x100_Black/Documents/Specyfikacja/Specyfikacja.pdf
security.capability failed: No data available
lremovexattr
root/Omega/Domains/Produkty_Typowe/Folders/Lustro_Omega_Plus/Documents
security.capability failed: No data available
lremovexattr
root/Omega/Domains/Produkty_Typowe/Folders/Lustro_Omega_Plus/Documents/Specyfikacja
security.capability failed: No data available
lremovexattr
root/Omega/Domains/Zakupy/Folders/ZK_84828/Parameters/Dokumenty
security.capability failed: No data available
My current version:
# btrfs --version
btrfs-progs v6.2
# uname -a
Linux orion 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1
(2024-11-22) x86_64 GNU/Linux
3. Are you using incremental streams, parent or clone subvols, etc?
Always incremental, always with parent, never with clones.
