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

[Stefan Lippers-Hollmann]

Hi

On 2015-07-31, Michael Biebl wrote:
> On Fri, 31 Jul 2015 08:08:38 +0200 Stefan Lippers-Hollmann
> <s.l-h at gmx.de> 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
> > > unfortunately not been recorded with an official Debian kernel, but
> > > I've been able to reproduce it with 4.0.0-2-amd64 as well. Just that I
> > > missed increasing the scrollback buffer in time and wasn't able to 
> > > fetch a full bootlog then - and, regardless of the kernel in use, 
> > > reproducing takes quite many reboots (too many for now) with full 
> > > logging enabled.
> > 
> > It took many reboots (>50), but here is a reproduction with the
> > official Debian kernel - gzipped logs attached.
> 
> Stefan, you are running amd64, right?

Yes, all affected systems are running unstable/ amd64. 

While I still use 3 non 64 bit capable i386 systems, I haven't powered 
them up often enough to be 100% sure about their status in this regard.

> 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 pvscan --background --cache --activate ay --major $major
> --minor $minor", ENV{LVM_SCANNED}="1"
> ...
> 
> If you build lvm2 on a systemd system, those rules look like
> ...
> ENV{SYSTEMD_READY}="1"
> ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run
> /sbin/lvm pvscan --cache $major:$minor", GOTO="lvm_end"
> ENV{SYSTEMD_ALIAS}="/dev/block/$major:$minor"
> ENV{ID_MODEL}="LVM PV $env{ID_FS_UUID_ENC} on /dev/$name"
> ENV{SYSTEMD_WANTS}="lvm2-pvscan@$major:$minor.service"
> 
> 
> 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. Can you copy the
> attached file to /etc/udev/rules.d/ and test if that fixes your problem?
[...]

I've done a local bin-NMU (on a systemd using chroot, so I ended up
with exactly the same lib/udev/rules.d/69-lvm-metad.rules you got), 
as that was easier to deploy and test locally - and it indeed seems
to fix the problem. Both the nforce4 system and the ivy-bridge system
used for reporting this bug have gone through >>20 successful reboots 
each and all other affected systems I've tested seem to be fixed as 
well (none of them having mdadm installed, I haven't been able to 
test the single system using mdadm+lvm2 so far).

Thanks a lot
	Stefan Lippers-Hollmann
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Digitale Signatur von OpenPGP
URL: <http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20150801/c9d86a45/attachment.sig>