Package: lvm2 Version: 2.03.02-3 Severity: critical Justification: breaks the whole system
The system with the latest kernel from testing and the latest lvm2 is unbootable when the root filesystem is a cached lvm volume. During boot, it says: device-mapper: table: 253:3: cache: Error creating cache's policy device-mapper: reload ioctl on (253:3) failed: Invalid argument /sbin/modprobe failed: 1 /sbin/modprobe failed: 1 This repeats a couple of times and it drops to the initramfs shell. From there, it's possible to boot by removing the cache: lvm lvchange --splitcache vg/root Then boot and reattach: lvconvert --type cache --cachepool root-cache vg/root I've seen #862136 but I'm not sure if it's the same (haven't tested). I tested all three policies (smq, mq, cleaner) during the troubleshoting and none worked. Another potential cause is this error that lvs throws after booting: Unknown feature in status: 8 171/2048 128 1897/81920 235 840 562 2581 0 1897 0 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw - Unknown feature in status: 8 337/3072 128 7578/163840 23719 28981 8025 4909 0 7578 0 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw - Unknown feature in status: 8 341/3072 128 7018/163840 3369 32447 96 77 0 7018 0 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw - Unknown feature in status: 8 341/3072 128 7018/163840 3369 32447 96 77 0 7018 0 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw - Unknown feature in status: 8 337/3072 128 7578/163840 23719 28981 8025 4909 0 7578 0 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw - Unknown feature in status: 8 171/2048 128 1897/81920 235 840 562 2581 0 1897 0 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw - (I have 3 cached partitions, it's 2 lines per partition) which sounds like there is something that lvm doesn't understand at boot (?) Note: the system was bootable with a much earlier kernel (4.19.0-4), probably with an older version of lvm2. I haven't tested falling back to that. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldoldstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lvm2 depends on: ii dmeventd 2:1.02.155-3 ii dmsetup 2:1.02.155-3 ii libaio1 0.3.112-5 ii libblkid1 2.34-0.1 ii libc6 2.29-2 ii libdevmapper-event1.02.1 2:1.02.155-3 ii libdevmapper1.02.1 2:1.02.155-3 ii libreadline5 5.2+dfsg-3+b13 ii libselinux1 2.9-2+b2 ii libsystemd0 242-7 ii libudev1 242-7 ii lsb-base 11.1.0 Versions of packages lvm2 recommends: ii thin-provisioning-tools 0.7.6-2.1 lvm2 suggests no packages. -- Configuration Files: /etc/lvm/lvm.conf changed [not included] -- debconf-show failed
