Package: lvm2 Version: 2.02.173-1 Followup-For: Bug #799295 Dear Maintainer, The same bug related to having to wait that LVM metatad bug persists, even after upgrade to Debian Buster.
*** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lvm2 depends on: ii dmeventd 2:1.02.142-1 ii dmsetup 2:1.02.142-1 ii init-system-helpers 1.50 ii libblkid1 2.30.2-0.1 ii libc6 2.24-17 ii libdevmapper-event1.02.1 2:1.02.142-1 ii libdevmapper1.02.1 2:1.02.142-1 ii liblvm2app2.2 2.02.173-1 ii libreadline5 5.2+dfsg-3+b1 ii libudev1 235-2 ii lsb-base 9.20170808 lvm2 recommends no packages. Versions of packages lvm2 suggests: pn thin-provisioning-tools <none> -- no debconf information