I had similar trouble, removing 'watch' didn't change a thing for me (can't seem to get any of these updates while in jaunty_beta?). I realize therefore my problem is not related to this bug, still I realize that more people will find this bug when searching for heir answer later; let me explain how I solved my issue for reference:
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 # takes ages /sbin/lvm lvremove vg/largish_snapshot /sbin/lvm vgchange -a n /sbin/lvm vgchange -a y # takes seconds 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. I'm 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 -- udev repeatedly generates "change" events for the same block device(s) https://bugs.launchpad.net/bugs/332270 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
