Some time ago there was a discussion about software raid and the new partitionability feature.
Since I upgraded to kernel 2.6.6-rc3 with libata I now have this feature inside the "native" kernel and want to try it out.
The dynamically allocated major number seems to be 254 (according to /proc/devices). This, however, could change when adding more dynamically allocating drivers. Am I right?
My main problem at this moment is how I can access the devices via /dev/something.
There should be something like /dev/md/d1p2 for example. This is not existing per se on a Debian woody system (no wonder). How can I make these entries, since mknod wants to have a major number to make these devices? Do I have to use a newer mknod? Or does my kernel lack some functionality? Perhaps then I wouldn´t need nodes at all?
One other thing: I put together a raid5 out of four identical sata hdds (dev/sda and so on), then partitioned it (md9) with fdisk. fdisk -l of the drives shows me no entries for sdb and sdc, however the following (similar for sda and sdd):
rossweisse:/# fdisk -l /dev/sdd
Disk /dev/sdd: 255 heads, 63 sectors, 19457 cylinders Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System /dev/sdd1 1 98 786434 83 Linux Partition 1 does not end on cylinder boundary: phys=(1023, 1, 4) should be (1023, 254, 63) /dev/sdd2 98 38950 312074260 83 Linux Partition 2 does not end on cylinder boundary: phys=(1023, 1, 4) should be (1023, 254, 63) /dev/sdd3 38950 58372 156011752 83 Linux Partition 3 does not end on cylinder boundary: phys=(1023, 1, 4) should be (1023, 254, 63)
Is this normal?
Thanks for any help, Norman.
--
Norman Schmidt Institut fuer Physikal. u. Theoret. Chemie
Dipl.-Chem. Univ. Friedrich-Alexander-Universitaet
schmidt@naa.net Erlangen-Nuernberg
IT-Systembetreuer Physikalische Chemie- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
