On Mon, Dec 06, 2004 at 12:37:52PM +0100, Lars Marowsky-Bree wrote:
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...
is it worth doing that in-kernel, i really believe that identifying
and starting arrays is a job that is better done in user-space.
regards,
L.
--
Luca Berra -- bluca@xxxxxxxxxx
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
-
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
