Your message dated Mon, 22 Feb 2021 22:18:51 +0000
with message-id <e1lejxx-0003je...@fasolo.debian.org>
and subject line Bug#946882: fixed in lvm2 2.03.11-2.1
has caused the Debian Bug report #946882,
regarding blkdeactive hardcodes wrong path to sort
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
946882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: lvm2
Source-Version: 2.03.11-2.1
Done: Ivo De Decker <iv...@debian.org>
We believe that the bug you reported is fixed in the latest version of
lvm2, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ivo De Decker <iv...@debian.org> (supplier of updated lvm2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 22 Feb 2021 21:39:14 +0000
Source: lvm2
Binary: dmeventd dmeventd-dbgsym dmsetup dmsetup-dbgsym dmsetup-udeb
libdevmapper-dev libdevmapper-event1.02.1 libdevmapper-event1.02.1-dbgsym
libdevmapper1.02.1 libdevmapper1.02.1-dbgsym libdevmapper1.02.1-udeb
liblvm2-dev liblvm2cmd2.03 liblvm2cmd2.03-dbgsym lvm2 lvm2-dbgsym lvm2-dbusd
lvm2-lockd lvm2-lockd-dbgsym lvm2-udeb
Architecture: source
Version: 2.03.11-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian LVM Team <team+...@tracker.debian.org>
Changed-By: Ivo De Decker <iv...@debian.org>
Description:
dmeventd - Linux Kernel Device Mapper event daemon
dmsetup - Linux Kernel Device Mapper userspace library
dmsetup-udeb - Linux Kernel Device Mapper userspace library (udeb)
libdevmapper-dev - Linux Kernel Device Mapper header files
libdevmapper-event1.02.1 - Linux Kernel Device Mapper event support library
libdevmapper1.02.1 - Linux Kernel Device Mapper userspace library
libdevmapper1.02.1-udeb - Linux Kernel Device Mapper userspace library (udeb)
liblvm2-dev - LVM2 libraries - development files
liblvm2cmd2.03 - LVM2 command library
lvm2 - Linux Logical Volume Manager
lvm2-dbusd - LVM2 D-Bus daemon
lvm2-lockd - LVM locking daemon
lvm2-udeb - Linux Logical Volume Manager (udeb)
Closes: 946882
Changes:
lvm2 (2.03.11-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add patch to fix path to sort in blkdeactivate. (closes: #946882)
Checksums-Sha1:
3bbf5bb587c6ddecd3b2c1d7ee09f9a2aba8700c 3077 lvm2_2.03.11-2.1.dsc
f00490baab52b83f334f6ca98021c41c28c083dd 32208 lvm2_2.03.11-2.1.debian.tar.xz
Checksums-Sha256:
eec3abca0730baa87b256ac69b9d0cc42b4aebd5ed494515cb1575dee1bbf3ab 3077
lvm2_2.03.11-2.1.dsc
7b7b8aaffdefdc99a8ae2f25928c2f0bfd0451c639db5c44c42e62f56c089cca 32208
lvm2_2.03.11-2.1.debian.tar.xz
Files:
5bbc8657b04e096fc6f59a2de56a318f 3077 admin optional lvm2_2.03.11-2.1.dsc
5c106b27d86b5460e4077d3892a13513 32208 admin optional
lvm2_2.03.11-2.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJKBAEBCAA0FiEE9GM4QTXwpzdLbkGwrEC7WJcE6vwFAmA0KSAWHGl2by5kZWRl
Y2tlckB1Z2VudC5iZQAKCRCsQLtYlwTq/CqwEACVd9SkcuGKQ0mn+G4dWmWsyMMN
se4li5I0noImnO+3m7rbx1jENhDBVBRwJxfr2oFGBsMAeoi9lDU7jZRX3KmR4psF
RH2VFnHBp8AM/uaSTmmgJLtEX87KAS4bNSTWCbZ782YQ4wWbsaS5tYBRgKy2SlRa
enXiqBGezK+iKmywpXUHHJ/CgvHj6A6+XDBuYMNWLON8aHgm9RlpZ4VphDSq248p
kCdsReFZdUXuiaKVfrMXt4LPrdOI4GHi9uOCsKWQw2L7Qh9Tu8XcTdFuZ7SKZXCk
khFB5b4JtVLqB6L73EDVCwFeyY5EYx8H49dy1Tbn/HQEKVa6pkRLXATRDM+IRewJ
j92L4zJNabNepDDhMqNhs/VDA72q885PJd2Wlla65NMjqpZUxlhAyPu19Tttl1Y7
OeAoU6oKJkvAN9YYnCekJzQG/ivUdrG0ZlyA3rNKZXihlrlXBYbjIEllmes5LD3x
EhoyLIZ3ps/MhiCsokyA+FaR6QOa/eFSZsM1oUUFauK3xquZbz+hookAWMSoSwMF
AD0ZJ8BTWYcf4P9VnYLrQyntF2uzAVv+KS8e7kvpNYL3IpuGS+V5Xsc1Wc8P6xkj
6ZkblDuMuVVrGbX7UrnKJuX+M3flRCGfGiivATiAX+SYtpDH0E1xRbNLaop6VidP
ldaU7WGmJ62LYUC6ew==
=y48T
-----END PGP SIGNATURE-----
--- End Message ---