> > OK. Maybe I wasn't clear enough.
> > 1. Partition a drive
> > 2. Reboot
> > 3. Now the kernel should see the partitions and let you create file
> > systems on them.
> >
> > You rebooted and fdisk sees the partitions now. Fine. Please try to
> > mke2fs /dev/md0p1
> > That should work. If it doesn't, devfs could be the problem.
>
> No, it should not. And devfs, for once, has nothing to do with it.
> RAID devices (md*) have _one_ (1) minor allocated to each. Consequently,
> they could not be partitioned by any kernel - there is no device numbers
> to be assigned to their partitions.
>
> > Could you please tell us which kernel version you're using?
>
> What would be much more interesting, which kernel are _you_ using
> and what device numbers, in your experience, do these partitions get?
I recall an MdPart patch for the kernel that would allow this, however, it
was way too buggy for real use. google for mdpart.
-- Lab tests show that use of micro$oft causes cancer in lab animals - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 07 2003 - 22:00:23 EST