Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Sean Caron <scaron@umich.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Automatically start two-level mdadm RAID arrays (i.e. RAID 60) on boot?
Date: Fri, 16 Feb 2018 02:02:17 +0500	[thread overview]
Message-ID: <20180216020217.2a9c7690@natsu> (raw)
In-Reply-To: <CAA43vkUG8LrMUjazeYFtGVKVuTvrYRPe-UcPb21r=xeYpctpmg@mail.gmail.com>

On Thu, 15 Feb 2018 15:41:37 -0500
Sean Caron <scaron@umich.edu> wrote:

> Hi all,
> 
> My site is very happily using MD RAID arrays constructed in two
> levels. That is to say, we do RAID 60 by constructing an mdadm RAID 0
> out of a number of mdadm RAID 6 strings.
> 
> These work great but one thing we have found and been living with is
> that, when the system boots, mdadm will automatically start all the
> RAID 6 strings, but it will not automatically start the top level RAID
> 0 container. The machine pauses on boot ("Hit S to skip, M to manually
> resolve") trying to mount the RAID because the device is not
> available, and a sys admin needs to manually go to the console and
> start the top level RAID 0 to continue the boot.

I had RAID5/6 with some members being RAID0s. IIRC it was a simple matter of
listing them in the correct order of initialization in mdadm.conf. Not sure if
this was strictly required, just that I did so right away (expecting that it
would be), and everything simply worked.

On the other hand, these days you likely have systemd, and it never misses its
chance to make people's lives much more interesting than that.

-- 
With respect,
Roman

  reply	other threads:[~2018-02-15 21:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 20:41 Automatically start two-level mdadm RAID arrays (i.e. RAID 60) on boot? Sean Caron
2018-02-15 21:02 ` Roman Mamedov [this message]
2018-02-15 21:51   ` Phil Turmel
2018-02-16  1:41     ` Brad Campbell
2018-02-16  2:17       ` Sean Caron
2018-02-16  3:53         ` Brad Campbell
2018-02-16  3:57           ` Brad Campbell
2018-02-16 11:00         ` Wolfgang Denk
2018-02-16 16:39           ` Sean Caron

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=20180216020217.2a9c7690@natsu \
    --to=rm@romanrm.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=scaron@umich.edu \
    /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