Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Roman Mamedov <rm@romanrm.ru>
Cc: CoolCold <coolthecold@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: MD does not wait for drives on start-up with kernels 3.8+
Date: Wed, 24 Apr 2013 17:12:48 +1000	[thread overview]
Message-ID: <20130424171248.235667a7@notabene.brown> (raw)
In-Reply-To: <20130415191157.72b630c3@natsu>

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

On Mon, 15 Apr 2013 19:11:57 +0600 Roman Mamedov <rm@romanrm.ru> wrote:

> On Mon, 15 Apr 2013 20:34:49 +1000
> NeilBrown <neilb@suse.de> wrote:
> 
> > > This was NOT required on any of the previous kernels, so I wonder why all of
> > > sudden with the 3.8+ kernels my system needs an extra "crutch" just to keep
> > > starting up properly.
> > 
> > This is almost certainly not directly related to the kernel.  It seems clear
> > that some change in the kernel has resulted in the difference, but it is
> > probably indirect and really a bug elsewhere.
> > 
> > What distro are you using?  Is systemd in use?
> 
> Debian Testing, no systemd.
> 

Can you try something for me?

Edit   /usr/share/initramfs-tools/scripts/local-top/mdadm

and just before the line:

  verbose && log_begin_msg "Assembling all MD arrays"

insert

  /sbin/udevadm settle

Then try booting without the 'rootdelay=10'.

If it doesn't (and the odds are at least even) then we have an awkward
situation.  The kernel is discovering devices asynchronously but it isn't
clear that there is any way to wait for it to "finish".

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2013-04-24  7:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-30 13:05 MD does not wait for drives on start-up with kernels 3.8+ Roman Mamedov
2013-03-31  5:36 ` CoolCold
2013-04-15  8:45   ` Roman Mamedov
2013-04-15 10:34     ` NeilBrown
2013-04-15 13:11       ` Roman Mamedov
2013-04-24  7:12         ` NeilBrown [this message]

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=20130424171248.235667a7@notabene.brown \
    --to=neilb@suse.de \
    --cc=coolthecold@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.ru \
    /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