Ok, my symptoms resolved: FWIW I found out that 'lvchange -a y' was taking ages on my volume group that contained a snaphot of 18Gb that was 50% full. Ages measuring in minutes, it would prevent successfull boot. I found out by doing repeated
/sbin/lvm vgchange -a n
/sbin/lvm vgchange -a y
/sbin/lvm lvremove vg/snapshot
/sbin/lvm vgchange -a n
/sbin/lvm vgchange -a y
Of course I made a backup of the data in the snapshot that I actually wanted to keep :)
Anyone seeing prolonged disk activity while failing boot, check this, or head over to bug #332270... I'm still considering to file this as a bug against lvm2 (unless I find some documentation on lvm2 that I should have read, stating that this behaviour is by design).
Ok, my symptoms resolved: FWIW I found out that 'lvchange -a y' was taking ages on my volume group that contained a snaphot of 18Gb that was 50% full. Ages measuring in minutes, it would prevent successfull boot. I found out by doing repeated
/sbin/lvm vgchange -a n
/sbin/lvm vgchange -a y
/sbin/lvm lvremove vg/snapshot
/sbin/lvm vgchange -a n
/sbin/lvm vgchange -a y
Of course I made a backup of the data in the snapshot that I actually wanted to keep :)
Anyone seeing prolonged disk activity while failing boot, check this, or head over to bug #332270... I'm still considering to file this as a bug against lvm2 (unless I find some documentation on lvm2 that I should have read, stating that this behaviour is by design).
Regards,
Seth