Dne 21.2.2012 11:22, Spelic napsal(a): > On 02/20/12 18:17, Zdenek Kabelac wrote: >> Dne 20.2.2012 16:09, Spelic napsal(a): >>> On 02/20/12 14:51, Mike Snitzer wrote: >>>> I've never seen this. Which distro are you using? >>> Ubuntu 11.04 64-bit but with vanilla 3.0.3 kernel >>> >>> Ubuntu's lvm: >>> # lvm version >>> LVM version: 2.02.66(2) (2010-05-20) >>> Library version: 1.02.48 (2010-05-20) >>> >> So I'd guess you might be a 'victim' of Debian home-brew udev rules for lvm2, >> which were unfortunately not consulted with upstream (nor udev, nor lvm). > > Indeed I have had a few bad experiences with Ubuntu's udev rules, but never > like this... > I don't think a wrong udev rule can hangup the whole machine with such > symptoms, you really think so? > > - lvs and/or "lvchange --refresh ..." processes hanging forever in kernel code > (and AFAIR it was in DM region, that's the /proc/pid/stack trace which I > unfortunately lost) lvs might be just waiting for unfinished lvchange process (lock holder) You could probably lock at 'gdb backtrace' to see for what it it waiting (or just use lvs -vvvv) There is probably an easy way to detect udev related problems - check for udev cookies waiting to be completed. 'dmsetup udevcookies' And you may manually force it's completion by: 'dmsetup udevcomplete_all' to see whether it will make lvchange to continue. > > - "sync" also cannot complete, so I can only do force reboot without flush > > -- > dm-devel mailing list > dm-devel@redhat.com We should probably keep this on linux-lvm list only as it's not dm related. Zdenek _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
