On 2004-12-03T16:34:59, Luca Berra <bluca@xxxxxxxxxx> wrote:
> > On boot, the kernel automatically detects and starts md0 through md4.
> > However, md5 is *not* autodetected. Using the RAID_AUTORUN ioctl also
> > has no effect. The only way I've found to reliably start md5 is to
> > have rc.sysinit run "mdadm -assemble --scan".
> >
> > Is this a bug? A design limitation? Something else?
> this is one of the limitations of the in-kernel autodetection
You can pull a fix for that one out of the SUSE kernel, where we add md
devices we just started to the auto detection. It worked pretty well in
2.4, but my memory is hazed when I try to recall whether it was all
ported to 2.6...
Sincerely,
Lars Marowsky-Brée <lmb@xxxxxxx>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
