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 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?
Just an update for the situation with lvm2 2.02.126-2: - all affected systems are running the amd64 architecture - all systems are up to date Debian unstable/main using initramfs-tools 0.120: - most systems are broken with lvm2 2.02.126-2, to varying degrees. the problem is apparently timing sensitive, systems using a SSD for the system paths (with their dedicated volume group) are less likely to fail booting, but occassionally they still do break. - doing a local bin-NMU of lvm2 2.02.126-2, in order to update /lib/udev/rules.d/69-lvm-metad.rules with the changes pointed out by Michael Biebl helps me on all non-mdadm == lvm2-only systems. Not a single failed boot on these systems so far. - lvm2 (2.02.126-2) on top of mdadm (RAID1) fails reliably for me, regardless of the bin-NMU for 69-lvm-metad.rules or staying on the plain lvm2 2.02.126-2; I'm aware of #793631 and just mention it because the update to lvm2 2.02.126-2 doesn't appear to make a difference. using dracut 040+1-1: - all lvm-only systems are booting fine, no local bin-NMU needed. - the mdadm(RAID1)+lvm2 system is also booting reliably, no local bin-NMU needed. - no issues found with the current lvm2 and dracut (but I obviously don't need any special initramfs hooks/ scripts) Regards Stefan Lippers-Hollmann
pgp69W1HNJxku.pgp
Description: Digitale Signatur von OpenPGP