Package: lvm2 Version: 2.03.11-2.1 Severity: normal Forwarded: https://github.com/lvmteam/lvm2/issues/18
Dear Maintainer, Sometimes there is a weird behavior causing some filesystems to be unmounted too early, when they are still needed. I have only found this problem in a box with lvm on top of RAID, but not in other boxes using lvm. Seems that this problem is related to lvm2. >From redhat bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1701234) The blk-availability.service unit is activated automatically when multipathd is enabled, even if multipathd is finally not used. This leads to the blk-availability service to unmount file systems too early, breaking unit ordering and leading to shutdown issues of custom services requiring some mount points. This has been reported upstream as https://github.com/lvmteam/lvm2/issues/18 and also to Ubuntu launchpad as https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832859 In the problematic box I have temporatily added "After=blk-availability.service" and seems to work around this problem. Seems that is not causing other problems, but will keep my fingers crossed. Regards, -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lvm2 depends on: ii dmeventd 2:1.02.175-2.1 ii dmsetup 2:1.02.175-2.1 ii init-system-helpers 1.60 ii libaio1 0.3.112-9 ii libblkid1 2.36.1-7 ii libc6 2.31-13 ii libdevmapper-event1.02.1 2:1.02.175-2.1 ii libedit2 3.1-20191231-2+b1 ii libselinux1 3.1-3 ii libsystemd0 247.3-6 ii libudev1 247.3-6 ii lsb-base 11.1.0 Versions of packages lvm2 recommends: pn thin-provisioning-tools <none> lvm2 suggests no packages. -- no debconf information -- Agustin
