Bug#865226: lvm2: lvmetad reproducibly fails on base Stretch install after lvrename
No Reply
noreply at aoeu.uk
Tue Jun 20 00:29:16 UTC 2017
Package: lvm2
Version: 2.02.168-2
Severity: normal
Dear Maintainer,
lvm2-lvmetad reproducibly shows poor boot-time behaviour after an lvrename; 'pvscan --cache' does not resolve. Discovered when attempting to rename the swap_1 lv that was created by the Debian Netinst x64 installer. Steps to reproduce:
Create ESXi 6.5 Debian 9 x64 VM:
1 CPU
2048 MB RAM
16 GB HDD
VMware PV SCSI
Edit VM:
Add CD Drive, Debian 9.0 x64 netinst ISO
Power on VM:
Graphical install, select default option/value for every choice except:
-root pw = debian
-user account name = debian
-user account password = debian
-disk setup: Guided - use entire disk and set up LVM, all files in one partition (or separate /var, /tmp, /home option, makes no difference to outcome)
-install grub to sda
Boot into VM:
-observe normal boot sequence, no lvm-related errors
-Log in as debian, start terminal, 'su -' to root
-swapoff -a
-lvrename /dev/debian-vg/swap_1 /dev/debian-vg/swap
-vi /etc/fstab, update swap entry location to /dev/mapper/debian--vg-swap
-reboot
Boot into VM again:
-observe "WARNING: Failed to connect to lvmetad. Falling back to device scanning.", "Failed to find logical volume "debian-vg/swap_1" messages repeated ~20-30x during elongated boot
-Log in as debian, start terminal, 'su -' to root
-systemctl status lvm2-lvmetad.service, observe it is active/running
-swapon -s, observe swap volume is correctly mounted
-lvs, observe correctly-named lv 'swap'
-pvscan --cache
-reboot
Boot into VM again:
-observe "WARNING: Failed to connect to lvmetad. Falling back to device scanning.", "Failed to find logical volume "debian-vg/swap_1" messages repeated ~20-30x during elongated boot
-Log in as debian, start terminal, 'su -' to root
-swapoff -a
-lvremove /dev/debian-vg/swap
-lvcreate -L 1g -n swap debian-vg
-observe warning about 'signature detected on /dev/debian-vg/swap at offset 4086'
Additional notes: 'vgscan --cache' and 'lvscan --cache' also appear to have no effect. Disabling lvm2-lvmetad.service appears to have no effect, boot messages remain the same. Same behaviour also seen in a VMware player VM, haven't tested other hypervisors or physical machines yet. Haven't tested volumes other than swap_1 as created by installer yet.
Possible similarities to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799295, but somewhat different setup and resulting error message; also this is Stretch.
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
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 /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lvm2 depends on:
ii dmeventd 2:1.02.137-2
ii dmsetup 2:1.02.137-2
ii init-system-helpers 1.48
ii libblkid1 2.29.2-1
ii libc6 2.24-11+deb9u1
ii libdevmapper-event1.02.1 2:1.02.137-2
ii libdevmapper1.02.1 2:1.02.137-2
ii liblvm2app2.2 2.02.168-2
ii libreadline5 5.2+dfsg-3+b1
ii libudev1 232-25
ii lsb-base 9.20161125
lvm2 recommends no packages.
Versions of packages lvm2 suggests:
pn thin-provisioning-tools <none>
-- no debconf information
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20170620/a2fade25/attachment.html>
More information about the pkg-lvm-maintainers
mailing list