Bug#826570: lvm2: erroneously starts lvmetad on upgrade
Matthew Vernon
mcv21 at cam.ac.uk
Mon Jun 6 13:11:54 UTC 2016
Package: lvm2
Version: 2.02.111-2.2+deb8u1
Severity: important
Hi,
Last night, my unattended guests upgraded their lvm2 (to the version
above) as part of an overnight update run. As a result of this,
lvmetad was started up despite use_lvmetad=0 in lvm.conf, and now lvm
commands are spitting out warnings of the form:
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
...this is giving me a lot of cron mail!
I think this is most likely the postinst erroneously thinking that
lvmetad was running and so asking systemd to (re-)start it. I have
checked my logs, though, and lvmetad hasn't run on this system as far
back as logs go.
Regards,
Matthew
-- System Information:
Debian Release: 8.5
APT prefers stable-backports
APT policy: (500, 'stable-backports'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lvm2 depends on:
ii dmeventd 2:1.02.90-2.2+deb8u1
ii dmsetup 2:1.02.90-2.2+deb8u1
ii init-system-helpers 1.22
ii initscripts 2.88dsf-59
ii libc6 2.19-18+deb8u4
ii libdevmapper-event1.02.1 2:1.02.90-2.2+deb8u1
ii libdevmapper1.02.1 2:1.02.90-2.2+deb8u1
ii libreadline5 5.2+dfsg-2
ii libudev1 215-17+deb8u4
ii lsb-base 4.1+Debian13+nmu1
lvm2 recommends no packages.
Versions of packages lvm2 suggests:
ii thin-provisioning-tools 0.3.2-1
-- no debconf information
More information about the pkg-lvm-maintainers
mailing list