From: NeilBrown <neilb@suse.de>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: linux RAID <linux-raid@vger.kernel.org>
Subject: Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
Date: Mon, 31 Oct 2011 16:49:54 +1100 [thread overview]
Message-ID: <20111031164954.274dda14@notabene.brown> (raw)
In-Reply-To: <4EAE3352.8090409@fnarfbargle.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On Mon, 31 Oct 2011 13:34:10 +0800 Brad Campbell <lists2009@fnarfbargle.com>
wrote:
> On 31/10/11 13:04, Brad Campbell wrote:
> > On 31/10/11 10:08, NeilBrown wrote:
> >>
> >> Hi Linus et al,
> >>
> >> I just discovered a fairly serious flaw that I introduced into 3.1 -
> >> details
> >> below.
> >>
> >> Anyone running RAID10 with 3.1 is advised to either apply this patch or
> >> revert an earlier kernel as soon as possible. In the mean time, remove
> >> any
> >> hot spares from an RAID10 array.
> >>
> >
> > G'day Neil,
> >
> > Is that the issue I bumped up against here?
> >
> > http://permalink.gmane.org/gmane.linux.raid/35805
>
> After looking closer I can confirm that making the indicated change
> resolves this problem.
Yes, definitely the same problem.
It's a shame I didn't pay proper attention to that report at the time - I
think that was the day that the uSD in my phone died and I was somewhat
distracted trying to figure out how to rebuild the install from scratch :-(
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-10-31 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 2:08 PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare NeilBrown
2011-10-31 5:04 ` Brad Campbell
2011-10-31 5:34 ` Brad Campbell
2011-10-31 5:49 ` NeilBrown [this message]
2011-10-31 6:10 ` Brad Campbell
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=20111031164954.274dda14@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists2009@fnarfbargle.com \
/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