Hi, On Tue, 29 Aug 2023 17:25:23 +0200 Friedrich Weber <f.we...@proxmox.com> wrote: > I'm seeing this bug in a different usecase on Debian Bookworm with LVM > 2.03.16-2: multipath is set up, the multipath device is an LVM > physical volume in a volume group with a thin pool. To prevent LVM from > picking up on the multipath components, /etc/lvm/lvm.conf has a > global_filter that rejects the multipath components by matching on their > /dev/disk/by-id symlink paths.
FWIW, for this usecase there seems to be a viable workaround: Instead of manually adding a global_filter that ignores multipath components, rely on LVM's own multipath component detection (available since LVM 2.03.13 [1]) that reads /etc/multipath/wwids. Installing multipath-tools-boot makes this file available in initramfs, and then detection also works in early boot. The description of multipath-tools-boot states that it should not be installed if not booting from a multipath device, but currently I don't see any downside of installing it here (not booting from a multipath device). Still, is there a chance the mentioned patches could be backported? Without them, global_filter is not functioning as expected. > https://sourceware.org/git/?p=lvm2.git;a=commit;h=17a3585cbb55d9a15ced9775a18b50c53a50ee8e > https://sourceware.org/git/?p=lvm2.git;a=commit;h=c9fdc828ff0504bc2e57f65862bc382f7663a8a2 > https://sourceware.org/git/?p=lvm2.git;a=commit;h=6d14144d311fb347e4225ad6a48d4900b39445c4 > https://sourceware.org/git/?p=lvm2.git;a=commit;h=bd05318ba2fc588be6339f5dc61f09195996b0e9 Best, Friedrich [1] https://gitlab.com/lvmteam/lvm2/-/commit/90485650931d3fc04d00c92a729050c8743969e5 [2] https://packages.debian.org/bookworm/multipath-tools-boot
