linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Phil Turmel <philip@turmel.org>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: md prefered minor has been renumbered
Date: Mon, 28 Nov 2016 20:39:17 +0000	[thread overview]
Message-ID: <583C95F5.9000701@youngman.org.uk> (raw)
In-Reply-To: <7b7ed841-7fe7-627d-bdb5-edb8c7d6a894@turmel.org>

On 28/11/16 20:22, Phil Turmel wrote:
> On 11/28/2016 03:02 PM, Wols Lists wrote:
> 
>> In My Experience (I'll probably get told I'm wrong :-) mdadm.conf seems
>> to be pretty much ignored by modern systems. And md numbers now by
>> default count down from 127, not up from 0.
> 
> mdadm.conf is *not* ignored.  Defaults are taken if it isn't found, or
> doesn't contain the info needed.

I did say IME :-)
> 
> Most modern systems have two copies of mdadm.conf.  One in the initramfs
> so you can boot a root filesystem that is inside an array, and the other
> in your root filesystem to assemble everything else.

Mine don't appear to have any ... and when I've tried to create one, it
was ignored. Of course, that doesn't rule out incompetence on my part
:-) But it means the defaults are perfectly okay for me :-) and probably
most people most of the time ...
> 
> Most distros copy the latter to the former when updating the initramfs.
> You may have to manually trigger this operation when you are
> re-arranging your arrays.
> 
> You also have to manually intervene if you want your initramfs to have
> a different mdadm.conf, like a two-phase assembly.
> 
> mdadm has been counting down from 127 for as long as I've used it.

I think I created several of my arrays as md0/1/2. And they stayed that
way for a little while before deciding to renumber.
> 
> Phil
> 
Cheers,
Wol

  reply	other threads:[~2016-11-28 20:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BC4985417D7F7B49B9AB545333BDB61B191FE1A2@Exchange-MBX1.esf.edu>
2016-11-28 17:26 ` md prefered minor has been renumbered Randall C. Grimshaw
2016-11-28 19:58   ` Phil Turmel
2016-11-28 20:34     ` Randall C. Grimshaw
2016-11-28 22:10       ` Randall C. Grimshaw
2016-11-28 22:12       ` Phil Turmel
     [not found]         ` <BC4985417D7F7B49B9AB545333BDB61B191FE29B@Exchange-MBX1.esf.edu>
2016-11-28 23:10           ` Phil Turmel
2016-11-29  1:12             ` Randall C. Grimshaw
2016-11-28 20:02   ` Wols Lists
2016-11-28 20:22     ` Phil Turmel
2016-11-28 20:39       ` Wols Lists [this message]
2016-11-28 22:06         ` Phil Turmel

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=583C95F5.9000701@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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;
as well as URLs for NNTP newsgroup(s).