The special thing on this system is, that it is used as virtual server
host system and logical volumes contain volume groups for the guest
systems. After debugging with udev debug output, I got this relevant
message:
. . .
udevd-work[173]: creating link '/dev/SAS/vb-flat-fast' to '/dev/dm-5'
udevd-work[173]: creating symlink '/dev/SAS/vb-flat-fast' to '../dm-5'
udevd-work[173]: created db file '/dev/.udev/data/b251:5' for
'/devices/virtual/block/dm-5'
udevd-work[173]: 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange
-a y'' started
After this the system stalls.
1. The LVs containing on the system VG are not fully processed yet. The LV
containing the root is not yet available.
2. The above LV is the first containing another VG, which triggers another
vgchange.
So the problem seams to be a deadlock situation when recursively
activating volume groups.
I did fix the problem by overriding the 85-lvm2.rules udev rule in
/etc/udev/rules.d/85-lvm2.rules:
---snip---
# override default 85-lvm2.rules and don't run vgchange recursively on LV
devices (ENV{DM_LV_NAME}=="")
# 2011-05-29;jw
SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_FS_TYPE}=="lvm*|LVM*",
ENV{DM_LV_NAME}=="" \
RUN+="watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'"
---snip---
And "update-initramfs -u".
It must be noted that the same system boots fine with Lucid without this
modification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789930
Title:
[natty] boot hangs / udev vgchange deadlock in nested vgs?
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
