From: Luca Berra <bluca@comedia.it>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Array over arrays - how to autoassemble correctly?
Date: Sat, 30 Jan 2010 11:17:36 +0100 [thread overview]
Message-ID: <20100130101735.GE15471@maude.comedia.it> (raw)
In-Reply-To: <73e903671001271032q1802c678i860744c72e2a92f3@mail.gmail.com>
On Wed, Jan 27, 2010 at 06:32:57PM +0000, Kristleifur Daðason wrote:
>Hi all,
>
>I'm running a RAID-60 array with mdadm. There are two RAID6 arrays,
>/dev/md/d0 and d1, and then a RAID0 "meta-array" over that,
>/dev/md/tank.
>
>What happens on boot is that the d0 and d1 arrays are assembled, but
>the tank array isn't - Ubuntu drops me to a root shell because it
>couldn't find the tank partition for mounting from fstab. However, I
>just have to do a simple 'mdadm --assemble --scan', and the tank array
>pops up instantly and everything is fine.
>
>How do I instruct mdadm to wait for d0 and d1 and do kind of a second
>assembly pass to construct tank over them?
>
>/proc/mdstat, output of 'mdadm --detail --scan' and
>/etc/mdadm/mdadm.conf are included. I hope that's enough background
>information.
I tested it again, "mdadm --assemble --scan" is able to start stacked
arrays correctly either with a configuration similar to yours or with no
configuration at all !!!
Maybe it is due to how ubuntu tries to assemble your array, i would
guess through udev rules.
Maybe the rules are triggered for real devices (/dev/sd*) and not for
/dev/md*, but im not running ubuntu, so i have no way to know.
Regards,
L.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-01-30 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 18:32 Array over arrays - how to autoassemble correctly? Kristleifur Daðason
2010-01-27 19:41 ` Luca Berra
2010-01-27 19:45 ` Kristleifur Daðason
2010-01-27 20:51 ` Goswin von Brederlow
2010-01-30 10:17 ` Luca Berra [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=20100130101735.GE15471@maude.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