linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: lrhorer@satx.rr.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Nested RAID and booting
Date: Tue, 21 Jun 2011 10:28:17 -0400	[thread overview]
Message-ID: <4E00AA81.2030100@cfl.rr.com> (raw)
In-Reply-To: <D1.7A.00666.3AE0FED4@cdptpa-omtalb.mail.rr.com>

These days most ( all? ) distributions use udev for plug and play.  When 
the physical disks are detected, udev notices ( with blkid ) that they 
are raid members, and runs mdadm --incremental on them.  Once they are 
all detected, the array goes active, and udev runs blkid on the array, 
notices that is a component, and runs mdadm --incremental on that.

On 6/8/2011 1:54 AM, Leslie Rhorer wrote:
>
> 	For financial reasons, I have had to temporarily create two members
> of a RAID6 array by first creating a pair of RAID0 arrays from four member
> disks.  The RAID6 array is currently re-shaping, and so far all seems well.
> I do have a concern about what will happen when the system reboots, however.
> In order to properly assemble the RAID6 array, the two RAID0 arrays will
> first need to be assembled and running, correct?  How do I guarantee the two
> RAID0 arrays will be up before mdadm attempts to assemble the RAID6 array?
> Will simply putting them in the mdadm.conf file prior to the RAID6 array do
> the trick?


      parent reply	other threads:[~2011-06-21 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  5:54 Nested RAID and booting Leslie Rhorer
2011-06-08  7:27 ` Roman Mamedov
2011-06-21 14:28 ` Phillip Susi [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=4E00AA81.2030100@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.com \
    /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).