On Thu, Dec 07, 2006, Loïc Minier wrote: > So, if the device-mapper table errors you are seeing in the verbose > lilo run are the fatal part and the problem we are trying to solve, the > next steps I would see are: > - check why running ioctls on dm-* devices fails (is it bad style? > should we create /dev/mapper/dm-* devices? why does it fail when we > pass a full device path?); perhaps we can fix the problem at the > libdevmapper level and make dmsetup table /dev/dm-1 work > - if it's incorrect to use /dev/dm-* nowadays, or if we can't tell, > blacklist /dev/dm-* from the lilo device map
Thinking about the problem again, I checked the dmsetup man page and saw that it mention "device_name" as a parameter to commands. I think that this device_name is a different name space than device nodes under /dev; this just happen to be named with the same name. I think lilo can continue merging the devices with the same major minor, but the RAID 1 support code should not blindly use lilo's device names, it should translate major:minor into a device mapper "device_name" first, for example via "info": bee:~# file /dev/dm-1 /dev/dm-1: block special (253/1) bee:~# dmsetup info -c --noheadings -j 253 -m 1 bee--sata-refuge:253:1:L--w:1:1:0:LVM-beM0G1UiiCSaWGi1RkcyX3EhGET9D7GbyLPU0wXiCsOswbyC2LoECortBYa3prWw bee:~# dmsetup table bee--sata-refuge 0 131072 linear 8:2 117440896 -- Loïc Minier <[EMAIL PROTECTED]>
