LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Marc Perkel <mperkel@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Raid 10 question/problem [ot]
Date: Sun, 28 Jan 2007 22:44:16 +0300	[thread overview]
Message-ID: <45BCFD10.4070302@tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.61.0701281327180.22295@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
> On Jan 28 2007 12:05, Michael Tokarev wrote:
[]
>> Mdadm creates those nodes automa[tg]ically - man mdadm, search for --auto.
> 
> Note that `mdadm -As` _is_ run on FC6 boot.

See above -- man mdadm, search for --auto.  -A = --assemble, -s = --scan.

>> In order for an md array to be started up on boot, it has to be specified
>> in /etc/mdadm.conf.  With proper DEVICE line in there.  That's all.
> 
> That's how it is, and it does not work.

Sure.  Because of this missing --auto flag.

> openSUSE 10.2:
> no mdadm.conf _at all_, /etc/init.d/boot.d/boot.md is chkconfig'ed _out_,
> _no_ md kernel module is loaded, and I still have all the /dev/md nodes.

And no udev.  Or, alternatively, *all* md devices are created by some other
script or somesuch.  There's No Magic (tm).

[]
> # mdadm -C /dev/md1 -e 1.0 -l 1 -n 2 /dev/sdb2 /dev/sdc2
> mdadm: error opening /dev/md1: No such file or directory
> 
> Showstopper.

Nonsense.  See above again, man mdadm, search for --auto.

[]
> You see, I have all the reason to be confused.

Yeah, this is quite... confusing.

It's all due to the way how mdadm iteracts with the kernel and how
udev works - all together.  The thing is - in order to assemble an
array, proper device node has to be in place.  But udev wont create
it until array is assembled.  Chicken&eggs problem.

Exactly due to this, the node(s) can be created with mdadm (with --auto
option, whicih can be specified in mdadm.conf too), AND/OR with some
startup script before invoking mdadm, AND/OR when the system isn't
broken by udevd (with ol'good static /dev).

>> But in any case, this has exactly nothing to do with kernel.
>> It's 100% userspace issues, I'd say distribution-specific issues.

..And each distribution uses its own kludge/workaround/solution for
this stuff - which you demonstrated... ;)

/mjt

  reply	other threads:[~2007-01-28 19:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-27 18:00 Marc Perkel
2007-01-27 18:09 ` Jan Engelhardt
2007-01-27 18:31   ` Marc Perkel
2007-01-27 18:32     ` Jan Engelhardt
2007-01-27 18:42       ` Marc Perkel
2007-01-27 20:59         ` Jan Engelhardt
2007-01-27 18:52       ` Marc Perkel
2007-01-28  9:05       ` Michael Tokarev
2007-01-28 12:40         ` Jan Engelhardt
2007-01-28 19:44           ` Michael Tokarev [this message]
2007-01-28 21:45             ` Jan Engelhardt
2007-01-28 17:38 ` Bill Davidsen
2007-01-28 19:49   ` Michael Tokarev
2007-01-28 21:40     ` Jan Engelhardt
2007-01-29 15:17     ` Bill Davidsen

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=45BCFD10.4070302@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mperkel@yahoo.com \
    --subject='Re: Raid 10 question/problem [ot]' \
    /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

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).