linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Backlund <tmb@mandriva.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: md raid10 regression in 2.6.27.4 (possibly earlier)
Date: Mon, 03 Nov 2008 01:51:21 +0200	[thread overview]
Message-ID: <490E3CF9.20208@mandriva.org> (raw)
In-Reply-To: <490DE55F.6080600@mandriva.org>

Thomas Backlund skrev:
> Peter Rabbitson skrev:
>> Hi,
>>
>> Some weeks ago I upgraded from 2.6.23 to 2.6.27.4. After a failed hard
>> drive I realized that re-adding drives to a degraded raid10 no longer
>> works (it adds the drive as a spare and never starts a resync). Booting
>> back into the old .23 kernel allowed me to complete and resync the array
>> as usual. Attached find a test case reliably failing on vanilla 2.6.27.4
>> with no patches.
>>
> 
> I've just been hit with the same problem...
> 
> I have a brand new server setup with 2.6.27.4 x86_64 kernel and a mix of
> raid0, raid1, raid5 & raid10 partitions like this:

And an extra datapoint.

Booting into 2.6.26.5 triggers an instant resync of the spare disks, so 
it means we have a regression between 2.6.26.5 and 2.6.27.4

If no-one have a good suggestion to try, I'll start bisecting tomorrow...
--
Thomas

  reply	other threads:[~2008-11-02 23:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02 11:27 mdraid10 regression in 2.6.27.4 (possibly earlier) Peter Rabbitson
2008-11-02 17:37 ` md raid10 " Thomas Backlund
2008-11-02 23:51   ` Thomas Backlund [this message]
2008-11-03 18:09     ` Thomas Backlund
2008-11-03 18:28       ` Justin Piszcz
2008-11-05 23:30     ` md raid10 regression in 2.6.27.4 (possibly earlier) BISECTED Thomas Backlund
2008-11-06  6:18       ` Neil Brown
2008-11-06  9:23         ` Thomas Backlund

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=490E3CF9.20208@mandriva.org \
    --to=tmb@mandriva.org \
    --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).