From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: stacked raid devices not autodetected?
Date: Mon, 6 Dec 2004 12:49:24 +0100 [thread overview]
Message-ID: <20041206114923.GF4693@percy.comedia.it> (raw)
In-Reply-To: <20041206113752.GM3858@marowsky-bree.de>
On Mon, Dec 06, 2004 at 12:37:52PM +0100, Lars Marowsky-Bree wrote:
>On 2004-12-03T16:34:59, Luca Berra <bluca@comedia.it> 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@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2004-12-06 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:32 stacked raid devices not autodetected? James Ralston
2004-12-03 15:34 ` Luca Berra
[not found] ` <36652.212.158.231.74.1102208997.squirrel@mail.fsck.co.uk>
2004-12-05 7:26 ` Luca Berra
2004-12-06 6:41 ` Odd md related top output with kernel 2.4.28 Guy
2004-12-06 7:15 ` Guy
[not found] ` <20041206113752.GM3858@marowsky-bree.de>
2004-12-06 11:49 ` Luca Berra [this message]
2004-12-06 13:16 ` stacked raid devices not autodetected? Lars Marowsky-Bree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041206114923.GF4693@percy.comedia.it \
--to=bluca@comedia.it \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).