From: marc@fox2k.net
To: linux-raid@vger.kernel.org
Subject: mdadm devices building in the wrong order
Date: Mon, 22 Oct 2007 19:44:37 -0500 (CDT) [thread overview]
Message-ID: <47710.64.230.0.49.1193100277.squirrel@fox2k.net> (raw)
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?
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!
next reply other threads:[~2007-10-23 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 0:44 marc [this message]
2007-10-23 2:28 ` mdadm devices building in the wrong order Neil Brown
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=47710.64.230.0.49.1193100277.squirrel@fox2k.net \
--to=marc@fox2k.net \
--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