All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: c.buhtz@posteo.jp, linux-raid@vger.kernel.org
Subject: Re: naming system of raid devices
Date: Sat, 2 Jan 2021 18:18:33 +0000	[thread overview]
Message-ID: <5FF0B8F9.3090501@youngman.org.uk> (raw)
In-Reply-To: <4D7R0G5b5cz9rxP@submission02.posteo.de>

On 02/01/21 15:39, c.buhtz@posteo.jp wrote:
> Thanks to you and all other answers. It helped me a lot to understand
> the backgrounds.
> 
> On 2021-01-01 14:09 Phil Turmel <philip@turmel.org> wrote:
>> I recommend creating an mdadm.conf file containing ARRAY entries for 
>> your desired setup.  Trim those lines to only have the desired name
>> and UUID.
> 
> Maybe I should open a new thread for that topic?
> Please correct me, because I am not an usual admin nor an mdadm expert.
> 
> I do not want to convince you with the following! I just want to bring
> up my point of view and my opinion to make it possible for you experts
> to "correct" me. ;)
> 
> I do not see the advantage of creating mdadm.conf.
> Via fstab I mount the devices by their UUID.
> And all other information's mdadm needs to use the RAID is stored in the
> superblock.

As the guy who looks after the wiki, none of my systems (to my best
knowledge) have or have had an mdadm.conf. There's supposed to be a way
to create it automagically from the current running config, but I've
never managed to get to grips with it ...
> 
> So information's in mdadm.conf would be redundant. And especially for
> a non-routine home-admin like me each conf-file I modify keep the
> possibility of misstakes/missconfigurations and more problems. Keeping
> it as simple as possible is very important for my environment.
> 
>> Once you are sure it works, I also recommend adding AUTO=-all to 
>> mdadm.conf, so any extra arrays you might plug in temporarily won't 
>> auto-assemble if still plugged in during boot.
> 
> I do not understand this. What does "auto-assemble" means? You mean if
> I plug in a SDD/HDD with a mdadm-created superblock?
> 
It's what happens when a system boots - as each drive is recognised,
it's added to an array until the array has enough drives to function. In
other words, rather than doing an mdadm assemble command with all the
drives, it's doing an assemble with just one drive at a time saying "add
to the relevant array".

If you've disabled auto-assemble, presumably you do need mdadm.conf to
tell mdadm what to assemble, which presumably also means you can't have
root on a raid because boot needs the array to find mdadm.conf in order
to start the array ... Don't quote me on that ...

Cheers,
Wol

  reply	other threads:[~2021-01-02 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-01 15:28 naming system of raid devices c.buhtz
2021-01-01 16:15 ` Reindl Harald
2021-01-01 19:09 ` Phil Turmel
2021-01-02 15:39   ` c.buhtz
2021-01-02 18:18     ` Wols Lists [this message]
2021-01-02 21:44       ` Rudy Zijlstra
2021-01-02 22:12     ` Rudy Zijlstra
2021-01-03 19:19       ` Anthony Youngman
2021-01-01 19:22 ` antlists

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=5FF0B8F9.3090501@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=c.buhtz@posteo.jp \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.