All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Candler <B.Candler@pobox.com>
To: NeilBrown <neilb@suse.de>
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 10:45:08 +0100	[thread overview]
Message-ID: <20120501094508.GA24134@nsrc.org> (raw)
In-Reply-To: <20120428080355.70585026@notabene.brown>

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 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 :-(

Regards,

Brian.

  parent reply	other threads:[~2012-05-01  9:45 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 [this message]
2012-05-01 10:18     ` NeilBrown
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=20120501094508.GA24134@nsrc.org \
    --to=b.candler@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.