On Sun, Aug 15, 2010 at 9:03 PM, Alasdair G Kergon <agk@xxxxxxxxxx> wrote: >> Just a vanilla linux. No udev. > > So likely a userspace problem where udev is now assumed to be present. > >> > Provide long listing of /dev/mapper and any dm/lvm devices in /dev. > > You can do that by running: > ls -l /dev/mapper /dev/vg01 > Also: > cat /proc/devices 253 device-mapper > cat /proc/misc 236 device-mapper <== was at 60 before the new kernel Got it! Sorry, it's me being _dumb_!!! With 2.6.35++, /dev/mapper/control has moved from 60 to 236! So I fix it by recreating the control file with "mknod /var/mapper/control c 10 253". I got this "internal error" when I activate/deactivate the volume group, but it seems ok. I could mount the volumes and so far it's all good. # vgchange -a n vg01 Internal error: Maps lock 14217216 < unlock 14221312 Internal error: Maps lock 14221312 < unlock 14225408 Internal error: Maps lock 14225408 < unlock 14229504 Internal error: Maps lock 14229504 < unlock 14233600 Internal error: Maps lock 14233600 < unlock 14237696 Internal error: Maps lock 14237696 < unlock 14241792 0 logical volume(s) in volume group "vg01" now active # vgchange -a y vg01 Internal error: Maps lock 14192640 < unlock 14196736 Internal error: Maps lock 14196736 < unlock 14200832 Internal error: Maps lock 14200832 < unlock 14204928 Internal error: Maps lock 14204928 < unlock 14209024 Internal error: Maps lock 14209024 < unlock 14213120 Internal error: Maps lock 14213120 < unlock 14217216 6 logical volume(s) in volume group "vg01" now active Hopefully those errors above means no harm. Thanks, Jeff -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
