Re: partitions in meta devices

Neil Brown (neilb@cse.unsw.edu.au)
Wed, 7 May 2003 10:06:18 +1000


On Monday May 5, wakko@animx.eu.org wrote:
> > > 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.

Unreported bugs don't get fixed ... or did I miss your report?

Work great for me on most of my servers.

NeilBrown
-
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/