Re: let md auto-detect 128+ raid members, fix potential race condition

[Luca Berra]

On Tue, Aug 01, 2006 at 05:46:38PM -0300, Alexandre Oliva wrote:
> Using the mkinitrd patch that I posted before, the result was that
> mdadm did try to bring up all raid devices but, because the raid456
> module was not loaded in initrd, the raid devices were left inactive.

probably your initrd is broken, it should not have even tried to bring
up an md array that was not needed to mount root.

> Then, when rc.sysinit tried to bring them up with mdadm -A -s, that
> did nothing to the inactive devices, since they didn't have to be
> assembled.  Adding --run didn't help.
>
> My current work-around is to add raid456 to initrd, but that's ugly.
> Scanning /proc/mdstat for inactive devices in rc.sysinit and doing
> mdadm --run on them is feasible, but it looks ugly and error-prone.
>
> Would it be reasonable to change mdadm so as to, erhm, disassemble ;-)
> the raid devices it tried to bring up but that, for whatever reason,
> it couldn't activate?  (say, missing module, not enough members,
> whatever)

this would make sense if it were an option, patches welcome :)

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-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/