Re: /dev/dm-0
Phillip Susi <[email protected]>
| Newsgroups | gmane.linux.ataraid |
|---|---|
| Message-ID | <[email protected]> |
I have /dev/mapper/via_hfciifae as the base raid device, and partitions on the device with a number appended to the above. I believe that the dmraid utility creates devices with this style of name, and if you are seeing /dev/dm-0 it is because udev is creating that node because as far as the kernel knows, the name of the device ( as exported by sysfs ) is "dm-0". Udev probably shouldn't be creating device nodes for device mapper devices, but if it does, you can simply ignore them. James Olson wrote: > Hi all, > I vote for not having a zero on the end of /dev/dm-0. In reading the previous posting I noticed that most linux utilities don't expect a 0 to indicate the entire harddisk or master boot area (the partition table). So that is why you can't install grub to /dev/dm-0 or fdisk -l /dev/dm-0. Now if it was changed to /dev/dm- you could do a grub install to /dev/dm- or and fdisk -l of it and it will see your partitions /dev/dm-1, /dev/dm-2 and so on and it would work with exisiting hard disk scripts and programs. (I know its ugly... perhaps /dev/dm, then /dev/dm1 /dev/dm2 and so on would be nicer looking). > -James > >