Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Sean Caron <scaron@umich.edu>
Cc: Brad Campbell <lists2009@fnarfbargle.com>,
	Phil Turmel <philip@turmel.org>, Roman Mamedov <rm@romanrm.net>,
	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 12:00:04 +0100	[thread overview]
Message-ID: <20180216110004.7DBF9240159@gemini.denx.de> (raw)
In-Reply-To: <CAA43vkW82nJXmwo7=HAhO+shx_Obak_tm7Vy0EKWW+HWW6brnw@mail.gmail.com>

Dear Sean,

In message <CAA43vkW82nJXmwo7=HAhO+shx_Obak_tm7Vy0EKWW+HWW6brnw@mail.gmail.com> you wrote:
>
> As it is now, we just populate /etc/mdadm/mdadm.conf ARRAY lines with
> the output of mdadm --examine --scan after building all the RAID 6
> strings and the top level RAID 0 container. This gives the result
> where the RAID 0 containers are the last lines in the file, after all
> the RAID 6 strings. For example, on a machine with RAID 6 strings
> md0...4 and RAID 0 string md5 (containing md0...md4), we have
> mdadm.conf contents like:

Just in case it is not clear (you didn't mention you did): after
generating /etc/mdadm/mdadm.conf you _must_ also rebuild the
initramfs image for your running kernel, so the new mdadm.conf gets
included there, where it is actually needed.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
I don't know if it's what you want, but it's what you get.  :-)
                      - Larry Wall in <10502@jpl-devvax.JPL.NASA.GOV>

  parent reply	other threads:[~2018-02-16 11:00 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
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 [this message]
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=20180216110004.7DBF9240159@gemini.denx.de \
    --to=wd@denx.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=philip@turmel.org \
    --cc=rm@romanrm.net \
    --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