Package: lvm2
Version: 2.03.02-3
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
On systems upgraded from stretch and without the usrmerge package installed,
/sbin/blkdeactivate (ExecStop= of blk-availability.service) gives the
following error during system shutdown:
blkdeactivate[12003]: /sbin/blkdeactivate: line 345: /bin/sort: No such
file or directory
Despite the error, I have not observed any adverse behavior.
However, on new installations or systems upgraded from stretch WITH the
usrmerge package installed, the error does not occur. Instead, filesystems
may be unmounted prematurely, for example those given as RequiresMountsFor=
in other units. I have observed data loss in this case where a required
mount was unmounted before the unit requiring it had properly saved its state
during shutdown.
I am not sure the best course of action to resolve this latter problem. Is it
necessary for blkdeactivate to be unmounting filesystems? Could the dependency
ordering be adjusted to avoid unmounting filesystems too soon?
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
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-3
ii libblkid1 2.33.1-0.1
ii libc6 2.28-10
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.8-1+b1
ii libsystemd0 241-7~deb10u2
ii libudev1 241-7~deb10u2
ii lsb-base 10.2019051400
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]
-- no debconf information
