From: Neil Brown <neilb@suse.de>
To: marc@fox2k.net
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm devices building in the wrong order
Date: Tue, 23 Oct 2007 12:28:36 +1000 [thread overview]
Message-ID: <18205.23636.513400.895816@notabene.brown> (raw)
In-Reply-To: message from marc@fox2k.net on Monday October 22
On Monday October 22, marc@fox2k.net wrote:
> Hello,
>
> I am having a rather urgent and annoying problem and I would appreciate
> some input from anyone who has come across this. I have not been able to
> find a solution as of yet. My issue deals with nested raid using mdadm,
> and it seems that upon a reboot mdadm is attempting to assemble the larger
> array before the smaller component array is created, and thus it is
> failing.
>
> I have a degraded raid 5 array md1 whch is composed of hda1 and md0. Upon
> a reboot, mdadm attempts to build md1 before md0 is built. It fails, so
> md1 is not build and I need to assemble it manually.
>
> Is there a solution for this?
What order are the arrays listed in in mdadm.conf?
If md1 comes first, put it last.
Otherwise, I cannot think what might be happening. Maybe if you
include some kernel logs that might help.
>
> Thanks you for your time,
>
> Marc
>
> p.s. I would like to also take a second to express my gratitude to Neil
> Brown for the mdadm utility. I have found it very useful and it has made
> working with raid in linux very enjoyable and straight-forward!
Thanks :-)
NeilBrown
prev parent reply other threads:[~2007-10-23 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 0:44 mdadm devices building in the wrong order marc
2007-10-23 2:28 ` Neil Brown [this message]
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=18205.23636.513400.895816@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=marc@fox2k.net \
/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