From: NeilBrown <neilb@suse.de>
To: Martin Wilck <mwilck@arcor.de>
Cc: Francis Moreau <francis.moro@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Accesses to not yet running array
Date: Mon, 26 Aug 2013 14:33:49 +1000 [thread overview]
Message-ID: <20130826143349.31afbefa@notabene.brown> (raw)
In-Reply-To: <5218FE4F.7000209@arcor.de>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
On Sat, 24 Aug 2013 20:41:19 +0200 Martin Wilck <mwilck@arcor.de> wrote:
> On 08/24/2013 02:42 PM, Francis Moreau wrote:
> > On Sat, Aug 24, 2013 at 2:40 PM, Francis Moreau <francis.moro@gmail.com> wrote:
> >> Hello Martin,
> >>
> >> On Fri, Aug 23, 2013 at 9:09 PM, Martin Wilck <mwilck@arcor.de> wrote:
> >>> On 08/23/2013 12:00 PM, Francis Moreau wrote:
> >>>
> >>>> [ adding Martin in CC since it seems related to DDF... ]
> >>>
> >>> I reproduced it here. The problem is that mdmon isn't running. Simply
> >>> try running "mdmon /dev/md127", and the mount should proceed.
> >>>
> >>
> >> oh, ok, I should have noticed.
> >>
> >>> You'd avoid the problem by running "mdadm -IR /dev/sda" in the first place.
> >>
> >> Actually this is how arrays are assembled during boot on some
> >> distributions (Fedora for example).
> >
> > I meant the sequence:
> >
> > mdadm -I /dev/sda
> > mdadm -I /dev/sdb
> > mdadm -R /dev/mdxxx
> >
> > is used by distribution.
>
> CentOS 6 uses the following sequence:
>
> mdadm -I /dev/sda
> mdadm -I /dev/sdb
> mdadm -I /dev/mdXXX
>
> I don't see mdadm -R anywhere on CentOS.
> You could change your udev rules to run "mdadm -IR /dev/mdXXX" instead.
> Have you tried that?
>
> I wonder if that woudn't be smarter anyway. Neil?
I don't think you want the udev rules to run "mdadm -IR ...".
If 'mdadm -IR...' to be run at all, it should probably be
mdadm -IRs
and it should happen after all attached busses have been scanned and udev has
processed all new devices.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-08-26 4:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 14:08 Accesses to not yet running array Francis Moreau
2013-08-20 23:06 ` NeilBrown
2013-08-21 13:57 ` Francis Moreau
2013-08-23 10:00 ` Francis Moreau
2013-08-23 19:09 ` Martin Wilck
2013-08-24 12:40 ` Francis Moreau
2013-08-24 12:42 ` Francis Moreau
2013-08-24 18:41 ` Martin Wilck
2013-08-26 4:33 ` NeilBrown [this message]
2013-08-27 8:11 ` Francis Moreau
2013-08-26 5:30 ` NeilBrown
2013-08-26 7:30 ` Francis Moreau
2013-08-26 7:53 ` NeilBrown
2013-08-26 8:16 ` Francis Moreau
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=20130826143349.31afbefa@notabene.brown \
--to=neilb@suse.de \
--cc=francis.moro@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mwilck@arcor.de \
/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