From: Michael Tokarev <mjt@tls.msk.ru>
To: Jim Paris <jim@jtan.com>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Assembly problems with kernel 2.6.30?
Date: Fri, 12 Jun 2009 12:00:03 +0400 [thread overview]
Message-ID: <4A320B03.5080009@msgid.tls.msk.ru> (raw)
In-Reply-To: <20090612023344.GA24806@psychosis.jim.sh>
Jim Paris wrote:
[]
> Weird: /dev/sdc2 has both a 0.90 and 1.0 superblock. I guess that's
> the problem. How would that have happened? mdadm --create over an
> existing device without a --zero-superblock inbetween, I suppose?
>
> I wonder why it was never a problem before. For the root, only
> /dev/sda2 and /dev/sdb2 are necessary. Maybe 2.6.30 changed the disk
> order, or the ordering of /proc/partitions, such that mdadm now
> examines this bad disk before the array is fully assembled, whereas it
> never needed to scan it before?
2.6.30 turned on "fastboot" option by default -- it's when
all disks/controllers gets scanned in parallel.
/mjt
prev parent reply other threads:[~2009-06-12 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 7:25 Assembly problems with kernel 2.6.30? Jim Paris
2009-06-12 1:33 ` Neil Brown
2009-06-12 2:33 ` Jim Paris
2009-06-12 8:00 ` Michael Tokarev [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=4A320B03.5080009@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jim@jtan.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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;
as well as URLs for NNTP newsgroup(s).