From: NeilBrown <neilb@suse.de>
To: Brian Candler <B.Candler@pobox.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: raid10 issues after reorder of boot drives.
Date: Tue, 1 May 2012 20:18:54 +1000 [thread overview]
Message-ID: <20120501201854.19f7def9@notabene.brown> (raw)
In-Reply-To: <20120501094508.GA24134@nsrc.org>
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
On Tue, 1 May 2012 10:45:08 +0100 Brian Candler <B.Candler@pobox.com> wrote:
> On Sat, Apr 28, 2012 at 08:03:55AM +1000, NeilBrown wrote:
> > I'm afraid you've been bitten by a rather nasty bug which is present in 3.3
> > and got back ported to some -stable kernel. The fix has been submitted and
> > should be appearing in -stable kernels soon (maybe already).
>
> Do you happen to know if this bug was present in ubuntu 11.10, kernel
> versions 3.0.0-15-server or 3.0.0-16-server ?
I don't keep track of what ubuntu (or anyone but suse) put in their kernels,
sorry.
>
> I saw failures to assemble RAID6 arrays after unclean shutdowns on both of
> these, just in test environments. If it happens again I'll send mdadm
> --examine output. I just tried to replicate it and failed :-(
To replicate:
- create an array.
- stop the array
- assemble the array with at least one missing device e.g.:
mdadm -A /dev/md0 /dev/sda1 /dev/sdb1
if it was a 3-device array
- check in /proc/mdstat that it is listed as "inactivate"
- reboot
- now "mdadm -E" the devices. If the raid level is -unknown- then the bug
has hit.
NeilBrown
>
> Regards,
>
> Brian.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-01 10:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 20:04 raid10 issues after reorder of boot drives likewhoa
2012-04-27 21:51 ` likewhoa
2012-04-27 22:05 ` NeilBrown
2012-04-27 23:29 ` likewhoa
2012-04-28 0:24 ` NeilBrown
2012-04-28 0:35 ` likewhoa
2012-04-28 2:37 ` likewhoa
2012-04-28 2:55 ` NeilBrown
2012-04-28 2:59 ` likewhoa
2012-04-28 3:23 ` NeilBrown
2012-04-28 3:51 ` likewhoa
2012-04-28 15:23 ` likewhoa
2012-04-28 21:28 ` NeilBrown
2012-04-29 14:23 ` likewhoa
2012-04-27 22:03 ` NeilBrown
2012-04-27 23:26 ` likewhoa
2012-05-01 9:45 ` Brian Candler
2012-05-01 10:18 ` NeilBrown [this message]
2012-05-01 11:15 ` Brian Candler
2012-05-02 2:37 ` linbloke
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=20120501201854.19f7def9@notabene.brown \
--to=neilb@suse.de \
--cc=B.Candler@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).