Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: linux-raid@vger.kernel.org
Subject: MD does not wait for drives on start-up with kernels 3.8+
Date: Sat, 30 Mar 2013 19:05:38 +0600	[thread overview]
Message-ID: <20130330190538.4e3c1771@natsu> (raw)

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

Hello,

I got a bizzare problem after trying to upgrade from 3.7.10 (which works fine)
to 3.8.3 or 3.9-rc3 (fail in the same way):

It looks like on the newer kernels MD does not wait for all drives to finish
registering before trying to bring up the arrays. As a result, on newer
kernels my arrays always come up with only 5 out of 7 members active.

dmesg 3.7.10:  http://romanrm.ru/dl/mdadm/dmesg37.txt
dmesg 3.9-rc3: http://romanrm.ru/dl/mdadm/dmesg39.txt

As you can see on 3.7.10 drives continue to go online until about 3.89sec
(Hitachi) and 4.26sec (card reader, unrelated), and only THEN, at 5.15sec the
md0 starts; it has all drives and everything is good.

On 3.9-rc3 (and 3.8.3), md0 tries to become active VERY EARLY at 2.64sec of
boot-up!!! Of course missing drives which appear later, and of those, members
of it should have been two Hitachi drives coming up at 3.33sec and 3.87sec.
So it starts degraded with 5 of 7 devices only.

What's up with this? I understand this might be not an md problem but an
udev(?) one; but how do I go about solving this?

-- 
With respect,
Roman

(resending this message since the previous one with largish attachments
didn't seem to make it to the list; also used a different dmesg for 3.7)

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

             reply	other threads:[~2013-03-30 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-30 13:05 Roman Mamedov [this message]
2013-03-31  5:36 ` MD does not wait for drives on start-up with kernels 3.8+ 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

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=20130330190538.4e3c1771@natsu \
    --to=rm@romanrm.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox