tw-netinstall:~ # snapper create --cleanup-algorithm number
Creating snapshot failed.
tw-netinstall:~ #
It’s your lucky day 
I was just testing out TW KDE in a VM and this happened to me.
The problem seems to be Discover/PackageKit holding a lock on zypp.
Killing it makes snapper work again. 
Edit: appears to be the kernel too. I was on 6.7.4 while it was working, not the 6.8.1 RC kernel that was pushed out to TW with the latest snapshot.
Confirmed: snapper not working with kernel 6.8.4-rc1-1-default but works with 6.7.4 and 6.8.1.
1 Like
Yep. The host got a bad kernel. Locked kernel-default and successfully tuped infamous host erlangen:
erlangen:~ # journalctl -b -1 -u transactional-update.service |grep -A2 -E 'following|Consumed'
Apr 08 13:46:51 erlangen transactional-update[31549]: The following 2 items are locked and will not be changed by any action:
Apr 08 13:46:51 erlangen transactional-update[31549]: Installed:
Apr 08 13:46:51 erlangen transactional-update[31549]: kernel-default-6.7.9-1.1 kernel-default-6.8.2-1.1
Apr 08 13:46:51 erlangen transactional-update[31549]: The following 97 packages are going to be upgraded:
Apr 08 13:46:51 erlangen transactional-update[31549]: apache2-mod_php8 avahi avahi-lang avahi-utils cpupower cpupower-lang fwupd fwupd-lang gdal girepository-1_0 gobject-introspection gtk4-lang gtk4-schema gtk4-tools kernel-firmware-all kernel-firmware-amdgpu kernel-firmware-ath10k kernel-firmware-ath11k kernel-firmware-ath12k kernel-firmware-atheros kernel-firmware-bluetooth kernel-firmware-bnx2 kernel-firmware-brcm kernel-firmware-chelsio kernel-firmware-dpaa2 kernel-firmware-i915 kernel-firmware-intel kernel-firmware-iwlwifi kernel-firmware-liquidio kernel-firmware-marvell kernel-firmware-media kernel-firmware-mediatek kernel-firmware-mellanox kernel-firmware-mwifiex kernel-firmware-network kernel-firmware-nfp kernel-firmware-nvidia kernel-firmware-platform kernel-firmware-prestera kernel-firmware-qcom kernel-firmware-qlogic kernel-firmware-radeon kernel-firmware-realtek kernel-firmware-serial kernel-firmware-sound kernel-firmware-ti kernel-firmware-ueagle kernel-firmware-usb-network kmod kmod-bash-completion libLLVM14 libLLVM15 libLLVM16 libLLVM17 libLLVM18 libavahi-client3 libavahi-common3 libavahi-core7 libavahi-glib1 libcanberra-gtk-module-common libcanberra-gtk0 libcanberra-gtk2-module libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra0 libclang-cpp14 libclang-cpp15 libclang-cpp16 libclang-cpp17 libclang-cpp18 libclang13 libcolord2 libcpupower1 libdns_sd libfwupd2 libgdal-drivers libgdal34 libgirepository-1_0-1 libgtk-4-1 libkmod2 libmpg123-0 libstemmer1d libx265-199 libzstd-devel libzstd1 mpg123-openal openSUSE-release openSUSE-release-appliance-custom php8 php8-cli python3-GDAL tcsh tcsh-lang typelib-1_0-Fwupd-2_0 ucode-amd xdm zstd
Apr 08 13:46:51 erlangen transactional-update[31549]: The following product is going to be upgraded:
Apr 08 13:46:51 erlangen transactional-update[31549]: openSUSE Tumbleweed
Apr 08 13:46:51 erlangen transactional-update[31549]: 20240404-0 -> 20240405-0
--
Apr 08 13:47:47 erlangen systemd[1]: transactional-update.service: Consumed 58.193s CPU time.
erlangen:~ #
All good here with snapper on MicroOS, Aeon and transactional update… through the kernel update 0405 and today’s 0407 snapshot.
Oh that’s interesting, MicroOS should be on the same kernel 6.8.4-rc1-1-default as TW right?
It did seem odd to me that snapper/libsnapper itself didn’t change versions between the working and non-working snapshots so it must be something else that’s causing the breakage. Wonder how the kernel ties into all this 
@pavinjoseph correct it tracks Tumbleweed. It’s the only systems I’m running snapper on, so I’ve moved to the new kernel and (tu) dupped to a new snapshot and snapper did it’s thing. I suspect you have a more deeper issue.
kernel-default search returns:
erlangen:/boot # zypper search --details --match-exact kernel-default
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------+---------+-----------+--------+-----------------------
il | kernel-default | package | 6.8.2-1.1 | x86_64 | (System Packages)
il | kernel-default | package | 6.7.9-1.1 | x86_64 | (System Packages)
vl | kernel-default | package | 6.8.4-1.1 | x86_64 | Haupt-Repository (OSS)
erlangen:/boot #
Version 6.8.2-1.1 works. Version 6.8.4-1.1 breaks snapper.
Dup to 20240405 resulted in the following mess:
erlangen:/boot # ll /.snapshots/3328/snapshot/boot/
total 135924
lrwxrwxrwx 1 root root 48 Mar 15 03:42 .vmlinuz-6.7.9-1-default.hmac -> ../usr/lib/modules/6.7.9-1-default/.vmlinuz.hmac
lrwxrwxrwx 1 root root 48 Apr 6 14:27 .vmlinuz-6.8.2-1-default.hmac -> ../usr/lib/modules/6.8.2-1-default/.vmlinuz.hmac
lrwxrwxrwx 1 root root 52 Apr 8 04:25 .vmlinuz-6.8.4-rc1-1-default.hmac -> ../usr/lib/modules/6.8.4-rc1-1-default/.vmlinuz.hmac
lrwxrwxrwx 1 root root 33 Apr 8 04:25 .vmlinuz.hmac -> .vmlinuz-6.8.4-rc1-1-default.hmac
lrwxrwxrwx 1 root root 45 Mar 15 03:42 System.map-6.7.9-1-default -> ../usr/lib/modules/6.7.9-1-default/System.map
lrwxrwxrwx 1 root root 45 Apr 6 14:27 System.map-6.8.2-1-default -> ../usr/lib/modules/6.8.2-1-default/System.map
lrwxrwxrwx 1 root root 49 Apr 8 04:25 System.map-6.8.4-rc1-1-default -> ../usr/lib/modules/6.8.4-rc1-1-default/System.map
lrwxrwxrwx 1 root root 41 Mar 15 03:42 config-6.7.9-1-default -> ../usr/lib/modules/6.7.9-1-default/config
lrwxrwxrwx 1 root root 41 Apr 6 14:27 config-6.8.2-1-default -> ../usr/lib/modules/6.8.2-1-default/config
lrwxrwxrwx 1 root root 45 Apr 8 04:25 config-6.8.4-rc1-1-default -> ../usr/lib/modules/6.8.4-rc1-1-default/config
-rw-r--r-- 1 root root 0 Apr 8 04:25 do_purge_kernels
drwxr-xr-x 1 root root 0 Dec 1 2019 efi
drwxr-xr-x 1 root root 98 Apr 8 04:25 grub2
lrwxrwxrwx 1 root root 26 Apr 8 04:25 initrd -> initrd-6.8.4-rc1-1-default
-rw------- 1 root root 46279370 Apr 8 04:25 initrd-6.7.9-1-default
-rw------- 1 root root 46419010 Apr 8 04:26 initrd-6.8.2-1-default
-rw------- 1 root root 46408972 Apr 8 04:26 initrd-6.8.4-rc1-1-default
lrwxrwxrwx 1 root root 46 Mar 15 03:42 sysctl.conf-6.7.9-1-default -> ../usr/lib/modules/6.7.9-1-default/sysctl.conf
lrwxrwxrwx 1 root root 46 Apr 6 14:27 sysctl.conf-6.8.2-1-default -> ../usr/lib/modules/6.8.2-1-default/sysctl.conf
lrwxrwxrwx 1 root root 50 Apr 8 04:25 sysctl.conf-6.8.4-rc1-1-default -> ../usr/lib/modules/6.8.4-rc1-1-default/sysctl.conf
lrwxrwxrwx 1 root root 27 Apr 8 04:25 vmlinuz -> vmlinuz-6.8.4-rc1-1-default
lrwxrwxrwx 1 root root 42 Mar 15 03:42 vmlinuz-6.7.9-1-default -> ../usr/lib/modules/6.7.9-1-default/vmlinuz
lrwxrwxrwx 1 root root 42 Apr 6 14:27 vmlinuz-6.8.2-1-default -> ../usr/lib/modules/6.8.2-1-default/vmlinuz
lrwxrwxrwx 1 root root 46 Apr 8 04:25 vmlinuz-6.8.4-rc1-1-default -> ../usr/lib/modules/6.8.4-rc1-1-default/vmlinuz
erlangen:/boot #
Indeed, as we both have a non-standard config with btrfs quota disabled.
@karlmistelberger I did more testing with kernel 6.8.4 and these were my observations:
- Creating snapshot works without the
numbercleanup algorithm. - Commenting out the snapper config line
QGROUP="1/0"allows for creating snapshot withnumbercleanup algorithm.
I suppose the kernel update broke/fixed some ABI depending on how you look at it 
1 Like
Confirmed.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.