Bug#1024257: btrfs-progs: Backup fails with "multiple capabilities" at first, then "capability no data available"
Hello :) :)
W dniu 25.06.2024 o 01:33, Nicholas D Steeves pisze:
But I have once found that btrfs/send receive finished without any
errors (!), subvolumes were both
read-only, and file was missing on receiving side.
If you're still on bullseye (Debian 11), then Debian Backports may solve
this. Install btrfs-progs 6.2-1~bpo11+1. The kernel from backports may
also be required. Note that backports support for Debian 11 (bullseye)
will probably end within the next six months, so please consider
upgrading to Debian 12 (bookworm) at your earliest convenience.
I have moved to Debian version 12,
errors still presisted.
I have filed a bug on btrfs github.
Finally I have modified btrfs program a little bit — changed "error" to
"warning"
Here's how.
# apt-get update
# apt-get full-upgrade
# btrfs --version
btrfs-progs v6.2
# dpkg -l | grep btrfs
ii btrfs-progs 6.2-1 amd64
Checksumming Copy on Write Filesystem utilities
# sudo apt-get install build-essential
# apt-get build-dep btrfs-progs
# mkdir leszek
# cd leszek
# apt-get source btrfs-progs
# ls
btrfs-progs-6.2 btrfs-progs_6.2-1.debian.tar.xz btrfs-progs_6.2-1.dsc
btrfs-progs_6.2.orig.tar.xz
# cd btrfs-progs-6.2
# vi ...
# diff:
btrfs.c
217c217
< printf("%s\n", PACKAGE_STRING);
---
> printf("leszek-2023-12-17-%s\n", PACKAGE_STRING);
cmds/receive.c
868,869c868,869
< ret = -errno;
< error("lremovexattr %s %s failed: %m", path, name);
---
> ret = 0;
> warning("leszek 2023-12-17: lremovexattr %s %s failed:
%m", path, name);
# dpkg-buildpackage -b -uc -us
# ./btrfs --version
leszek-2023-12-17-btrfs-progs v6.2
# make static
Bug#1024257: btrfs-progs: Backup fails with "multiple capabilities" at first, then "capability no data available"
Hi Leszek, On Wed, 16 Nov 2022 14:50:28 +0100 Leszek Dubiel wrote: > Package: btrfs-progs > Version: 5.10.1-2 > Severity: important > > > Hello :) :) > > I am doing regular backukps send/receive. > > I get a lot of messages like this: > > WARNING: capabilities set multiple times per file: /mnt/sda2/2022-11-11 > 23:58:02 169205882/ZK_83308/Documents/fk-2228.jpg > > WARNING: capabilities set multiple times per file: /mnt/sdc2/2022-11-11 > 23:58:02 169205882/ZK_83308/Documents/fk-2228.jpg > > WARNING: capabilities set multiple times per file: /mnt/sdc2/2022-11-12 > 08:57:01 386278919/ZK_83308/Documents/fk-2228.jpg > > > and after some time it completely fails with errors: > > ERROR: lremovexattr ZK_83308/Documents/fk-2228.jpg security.capability > failed: No data available > > ERROR: lremovexattr ZK_83308/Documents/fk-2228.jpg security.capability > failed: No data available > > ERROR: lremovexattr ZK_83308/Documents/fk-2228.jpg security.capability > failed: No data available > > > > I have found other people also have such problems: > > https://github.com/digint/btrbk/issues/416 > > https://www.kubuntuforums.net/forum/general/miscellaneous/btrfs/71629-strange-warning-on-incremental-backup > > > > and the problem is probably back again after 2014: > > https://bugzilla.kernel.org/show_bug.cgi?id=68891 > > > > > After getting warnings I have checksummed send and receiving subvolumes > with rsync and files are > identical. > > But I have once found that btrfs/send receive finished without any > errors (!), subvolumes were both > read-only, and file was missing on receiving side. > > > > If you're still on bullseye (Debian 11), then Debian Backports may solve this. Install btrfs-progs 6.2-1~bpo11+1. The kernel from backports may also be required. Note that backports support for Debian 11 (bullseye) will probably end within the next six months, so please consider upgrading to Debian 12 (bookworm) at your earliest convenience. Regards, Nicholas signature.asc Description: PGP signature
Bug#1024257: btrfs-progs: Backup fails with "multiple capabilities" at first, then "capability no data available"
Package: btrfs-progs Version: 5.10.1-2 Severity: important Hello :) :) I am doing regular backukps send/receive. I get a lot of messages like this: WARNING: capabilities set multiple times per file: /mnt/sda2/2022-11-11 23:58:02 169205882/ZK_83308/Documents/fk-2228.jpg WARNING: capabilities set multiple times per file: /mnt/sdc2/2022-11-11 23:58:02 169205882/ZK_83308/Documents/fk-2228.jpg WARNING: capabilities set multiple times per file: /mnt/sdc2/2022-11-12 08:57:01 386278919/ZK_83308/Documents/fk-2228.jpg and after some time it completely fails with errors: ERROR: lremovexattr ZK_83308/Documents/fk-2228.jpg security.capability failed: No data available ERROR: lremovexattr ZK_83308/Documents/fk-2228.jpg security.capability failed: No data available ERROR: lremovexattr ZK_83308/Documents/fk-2228.jpg security.capability failed: No data available I have found other people also have such problems: https://github.com/digint/btrbk/issues/416 https://www.kubuntuforums.net/forum/general/miscellaneous/btrfs/71629-strange-warning-on-incremental-backup and the problem is probably back again after 2014: https://bugzilla.kernel.org/show_bug.cgi?id=68891 After getting warnings I have checksummed send and receiving subvolumes with rsync and files are identical. But I have once found that btrfs/send receive finished without any errors (!), subvolumes were both read-only, and file was missing on receiving side. -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-19-amd64 (SMP w/8 CPU threads) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages btrfs-progs depends on: ii libblkid1 2.36.1-8+deb11u1 ii libc6 2.31-13+deb11u5 ii libcom-err2 1.46.2-2 ii libext2fs2 1.46.2-2 ii libgcc-s1 10.2.1-6 ii liblzo2-2 2.10-2 ii libmount1 2.36.1-8+deb11u1 ii libuuid1 2.36.1-8+deb11u1 ii libzstd1 1.4.8+dfsg-2.1 ii zlib1g 1:1.2.11.dfsg-2+deb11u2 btrfs-progs recommends no packages. Versions of packages btrfs-progs suggests: pn duperemove -- no debconf information
