Bug#791869: marked as done (lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails)

age is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 791869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin M

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi As indicated in direct conversation, the changes in 2.02.126-3 seem to avoid the problem for me, both on lvm2-only and mdadm+lvm2 systems using initramfs-tools. Regards Stefan Lippers-Hollmann pgp27SI_U2zmC.pgp Description: Digitale Signatur von OpenPGP

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Fri, Jul 31, 2015 at 08:08:38AM +0200, Stefan Lippers-Hollmann wrote: > It took many reboots (>50), but here is a reproduction with the > official Debian kernel - gzipped logs attached. Okay, thank you. However it just shows that udev never processes the add event for sda2, so never runs pvsca

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi On 2015-08-01, Stefan Lippers-Hollmann wrote: > On 2015-07-31, Michael Biebl wrote: [...] > > Bastian built the lvm2 on amd64 on a non-systemd system, it seems. This > > results in /lib/udev/rules.d/69-lvm-metad.rules lookin like this: > > ... > > ENV{SYSTEMD_READY}="1" > > RUN+="/sbin/lvm pvsc

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Mon, 27 Jul 2015, Michael Biebl wrote: > > Not sure if that is happening here. But fixing [2] and making sure > pvscan is run via /bin/systemd-run look like should be done in any > case. > > Michael > > > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi On 2015-07-31, Michael Biebl wrote: > On Fri, 31 Jul 2015 08:08:38 +0200 Stefan Lippers-Hollmann > wrote: > > Hi > > > > On 2015-07-31, Stefan Lippers-Hollmann wrote: > > > On 2015-07-31, Stefan Lippers-Hollmann wrote: > > > > On 2015-07-25, Bastian Blank wrote: > > [...] > > > The attached b

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Am 31.07.2015 um 10:54 schrieb Michael Biebl: > If I replace /lib/udev/rules.d/69-lvm-metad.rules with the attached > file, my problems with LVM on top of RAID1 are gone. Grr, nvm. While testing, I actually had use_lvmetad disabled. Still getting failures, even with the modified 69-lvm-metad.rul

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Fri, 31 Jul 2015 08:08:38 +0200 Stefan Lippers-Hollmann wrote: > Hi > > On 2015-07-31, Stefan Lippers-Hollmann wrote: > > On 2015-07-31, Stefan Lippers-Hollmann wrote: > > > On 2015-07-25, Bastian Blank wrote: > [...] > > The attached bootlog (serial console && udev.log-priority=7) has > > un

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi On 2015-07-31, Stefan Lippers-Hollmann wrote: > On 2015-07-31, Stefan Lippers-Hollmann wrote: > > On 2015-07-25, Bastian Blank wrote: [...] > The attached bootlog (serial console && udev.log-priority=7) has > unfortunately not been recorded with an official Debian kernel, but > I've been able t

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi On 2015-07-31, Stefan Lippers-Hollmann wrote: > On 2015-07-25, Bastian Blank wrote: > > output (udev.log-priority=8 at the kernel command line) from a failed > > boot. [...] > Loading, please wait... > invalid udev.log[2.343952] random: systemd-udevd urandom read with 4 bits > of entropy a

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi On 2015-07-31, Stefan Lippers-Hollmann wrote: [...] > challenger:~# pvs > PV VGFmt Attr PSize PFree > /dev/sda2 vg-challenger lvm2 a-- 831,49g 251,49g > challenger:~# vgs > VG#PV #LV #SN Attr VSize VFree > vg-challenger 1 4 0 wz--n- 831

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi On 2015-07-25, Bastian Blank wrote: > On Tue, Jul 21, 2015 at 09:11:57PM +0200, Bastian Blank wrote: > > So the next step could be debugging udev and see what it calls and when. > > Please provide the complete udev db (udevadm info -e) and udev debugging attached (in the broken state) as nfor

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi Just confirming that there's no change with src:lvm2 2.02.126-1, the problem is still present. Regards Stefan Lippers-Hollmann pgpf6OM5kuNIg.pgp Description: Digitale Signatur von OpenPGP

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Am 28.07.2015 um 08:41 schrieb Bastian Blank: > On Mon, Jul 27, 2015 at 05:40:39PM +0200, Michael Biebl wrote: >> udev under systemd doesn't allow long running processes which background >> to be started from udev rules, such processes are killed by udevd [4]. >> Not sure if that is happening here.

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Mon, Jul 27, 2015 at 05:40:39PM +0200, Michael Biebl wrote: > udev under systemd doesn't allow long running processes which background > to be started from udev rules, such processes are killed by udevd [4]. > Not sure if that is happening here. But fixing [2] and making sure > pvscan is run via

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi Just for testing, I've tried using dracut as provider for linux-initramfs-tool instead of initramfs-tools. The results were positive, around 30 successful reboots - going back to initramfs-tools exposed the original problem right away again. I don't use any special initramfs-tools configurati

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Am 27.07.2015 um 07:56 schrieb Bastian Blank: > On Sun, Jul 26, 2015 at 12:24:43AM +0200, Michael Biebl wrote: >> Fwiw, I could easily and reliably reproduce this problem in a VM with >> LVM (guided setup with separate /, /home, /tmp, /var) on top of mdadm >> RAID1 with a minimal standard installat

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Am 27.07.2015 um 17:40 schrieb Michael Biebl: > Am 27.07.2015 um 07:56 schrieb Bastian Blank: >> On Sun, Jul 26, 2015 at 12:24:43AM +0200, Michael Biebl wrote: >>> Fwiw, I could easily and reliably reproduce this problem in a VM with >>> LVM (guided setup with separate /, /home, /tmp, /var) on top

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Just noticed this option is not yet documented! I've filed a report for udev guys to add mention this in the man page and describe it a bit since it's quite important and yet it's hidden functionality if not documented: https://bugzilla.redhat.com/show_bug.cgi?id=1247210 -- To UNSUBSCRIBE, ema

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On 07/27/2015 04:12 PM, Peter Rajnoha wrote: > It's the OPTIONS+="db_persist" that needs to be used in initramfs > for MD devices. This marks udev db records related to this device with > sticky bit then which is then recognized by udev code and the udev > db state is not cleaned up in that case:

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On 07/27/2015 03:57 PM, Peter Rajnoha wrote: > That's how it was supposed to work. I can imagine the problematic > part here may be the transfer of the udev database state from initramfs > to root fs - there is a special way that udev uses to mark devices > so that the udev db state is kept from in

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On 07/25/2015 09:34 PM, Bastian Blank wrote: > Hi Peter > > Currently I think that all this problems are related to missing or > broken pvscan --cache calls. > > I found one problematic case regarding coldplug; I believe Redhat does > not longer use this code path. In none of my tests the "artif

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Sat, Jul 25, 2015 at 04:15:58PM -0400, Rick Thomas wrote: > OK. We have a tentative diagnosis. That's good. Is there something I can > do to verify for sure that this is what's actually happening and give us a > clue as to what we need to do to fix it? In /lib/udev/rules.d/63-md-raid-array

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Sun, Jul 26, 2015 at 12:24:43AM +0200, Michael Biebl wrote: > Fwiw, I could easily and reliably reproduce this problem in a VM with > LVM (guided setup with separate /, /home, /tmp, /var) on top of mdadm > RAID1 with a minimal standard installation. There are at least two distinct problems. Th

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Sat, 25 Jul 2015 14:27:03 +0200 Bastian Blank wrote: > On Tue, Jul 21, 2015 at 09:11:57PM +0200, Bastian Blank wrote: > > So the next step could be debugging udev and see what it calls and when. > > Please provide the complete udev db (udevadm info -e) and udev debugging > output (udev.log-pri

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Jul 25, 2015, at 3:21 PM, Bastian Blank wrote: > On Tue, Jul 21, 2015 at 07:05:42PM -0700, Rick Thomas wrote: >> I created a virtual machine with VMWare running on my Mac. It has a virtual >> DVD-drive (loaded with the Jessie 8.1.0 amd64 install image) and three >> virtual disk drives. One

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi Peter Currently I think that all this problems are related to missing or broken pvscan --cache calls. I found one problematic case regarding coldplug; I believe Redhat does not longer use this code path. In none of my tests the "artificial" add event triggers pvscan as it should. The udev ru

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Tue, Jul 21, 2015 at 07:05:42PM -0700, Rick Thomas wrote: > I created a virtual machine with VMWare running on my Mac. It has a virtual > DVD-drive (loaded with the Jessie 8.1.0 amd64 install image) and three > virtual disk drives. One virtual disk is a small (1 GB) drive to hold /boot. >

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Tue, Jul 21, 2015 at 09:11:57PM +0200, Bastian Blank wrote: > So the next step could be debugging udev and see what it calls and when. Please provide the complete udev db (udevadm info -e) and udev debugging output (udev.log-priority=8 at the kernel command line) from a failed boot. As this bu

Bug#791869:

An alternative explanation is that my original hung update-initramfs that required "pvscan --cache" to complete created a broken or incomplete initramfs. -- Ben Caradoc-Davies Director Transient Software Limited New Zealand -- To UNSUBSCRIBE, email to debian-bugs-rc-re

Bug#791869: Info received (Bug#791869: System hangs on boot with lvmetad not active)

I am unable to reproduce this hang. When I re-enable lvmetad in lvm.conf and run "update-initramfs -u", reboot succeeds (many trials). Perhaps it is just the very intermittent failures on SSDs reported by Stefan? -- Ben Caradoc-Davies Director Transient Software Limited

Bug#791869: System hangs on boot with lvmetad not active

This bug now makes any kernel upgrade (in this case linux-image-4.0.0-2-amd64) cause the system to be unbootable. The system is unable to contact lvmetad and unable to locate the root partition. There is no luks passphrase prompt. Please upgrade this bug to CRITICAL. Or should I file a critica

Bug#791869: Infinite hang on update-initramfs

I have found new GRAVE manifestation of this bug. Rather than create a new bug report, I am adding it to this list. Should this be a new new GRAVE bug. Today I upgraded linux-image-4.0.0-2-amd64 to 4.0.8-2 and encountered an infinite hang in initramfs-tools while it was running vgs: /etc/ker

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Jul 21, 2015, at 12:11 PM, Bastian Blank wrote: > However I'm still unable to reproduce the problem > without a sledgehammer. I reproduced the problem in a tiny test system as follows: I created a virtual machine with VMWare running on my Mac. It has a virtual DVD-drive (loaded with the

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Tue, Jul 21, 2015 at 08:37:16PM +0200, Bastian Blank wrote: > Yeah. pvscan should be run by udev for each new device. For some > reason this either don't work, breaks in the middle or no idea what > happens. Okay, at least I can prove that removing pvscan breaks everything with similar effect

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Mon, Jul 20, 2015 at 11:11:43AM +1200, Ben Caradoc-Davies wrote: > Booting succeeds for me with / and /home on separate LVs in a single > crypto-luks PV (see lsblk below) with lvm2 2.02.122-2 amd64. However, after > updating to the latest lvm2, "pvscan", "pvs", "vgs", and "lvs" all hang > indefi

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi On 2015-07-20, Ben Caradoc-Davies wrote: > On Mon, 20 Jul 2015 01:16:12 +0200 Stefan Lippers-Hollmann > wrote: > > Interesting enough, systems using a SSD for the system > mountpoints usually succeed booting most of the time > > Thanks for this observation, Stefan. My successful boots are in

Bug#791869: Info received (Output of 'systemctl status' in broken state and just after un-breaking it...)

On a hunch, I made the following change > # diff /SAVE/etc/lvm/lvm.conf /etc/lvm/lvm.conf > 823c823 > < use_lvmetad = 1 > --- > > use_lvmetad = 0 and ran > # update-initramfs -u Then rebooted. The problem went away… As I understand it, this makes LVM always check the actual physical

Bug#791869: Output of 'systemctl status' in broken state and just after un-breaking it...

In case it helps, here’s systemctl status as logged during emergency shell. Rick Jul 19 22:43:49 stretch fixup[687]: + systemctl status Jul 19 22:43:49 stretch fixup[687]: * stretch Jul 19 22:43:49 stretch fixup[687]: State: maintenance Jul 19 22:43:49 stretch fixup[687]: Jobs: 0 queued

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Mon, 20 Jul 2015 01:16:12 +0200 Stefan Lippers-Hollmann wrote: Interesting enough, systems using a SSD for the system mountpoints usually succeed booting most of the time Thanks for this observation, Stefan. My successful boots are indeed on a system using an SSD. I have not yet had a fail

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Booting succeeds for me with / and /home on separate LVs in a single crypto-luks PV (see lsblk below) with lvm2 2.02.122-2 amd64. However, after updating to the latest lvm2, "pvscan", "pvs", "vgs", and "lvs" all hang indefinitely until I manually run "pvscan --cache". They worked fine with 2.02

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Hi On 2015-07-19, Bastian Blank wrote: > On Thu, Jul 09, 2015 at 05:16:57AM +0200, Stefan Lippers-Hollmann wrote: > > Upgrading src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting due to > > a new systemd unit dependency failures regarding lvmetad when mounting > > non-rootfs logical volumes.

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Thu, Jul 09, 2015 at 05:16:57AM +0200, Stefan Lippers-Hollmann wrote: > Upgrading src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting due to > a new systemd unit dependency failures regarding lvmetad when mounting > non-rootfs logical volumes. Jumping to the emergency shell and invoking > "

Bug#791869: 2.02.122-2 breaks booting, mounting LVs other than / fails

Package: lvm2 Version: 2.02.122-2 Followup-For: Bug #791869 Dear Maintainer, just to confirm, this bug is still in the latest version Regards Achim -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'u

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Package: lvm2 Version: 2.02.122-1 Hi there, I've got the same bug and I've had to downgrade the lvm2 packages too. Note: My partitions are encrypted. Regards, Marcelo --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 40 experiment

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Package: lvm2 Version: 2.02.122-1 Severity: serious Hi Upgrading src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting due to a new systemd unit dependency failures regarding lvmetad when mounting non-rootfs logical volumes. Jumping to the emergency shell and invoking "vgchange -ay" and "mount