From: Thomas Backlund <tmb@mandriva.org>
To: Neil Brown <neilb@suse.de>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: md raid10 regression in 2.6.27.4 (possibly earlier) BISECTED
Date: Thu, 06 Nov 2008 11:23:14 +0200 [thread overview]
Message-ID: <4912B782.2070409@mandriva.org> (raw)
In-Reply-To: <18706.35892.143554.833998@notabene.brown>
Neil Brown skrev:
> On Thursday November 6, tmb@mandriva.org wrote:
>> But anyway...
>>
>> This is the commit that breaks the raid10 rebuild/resync:
>
> Awesome. Thanks!
>
>> --- cut ---
>> 6c2fce2ef6b4821c21b5c42c7207cb9cf8c87eda is first bad commit
>> commit 6c2fce2ef6b4821c21b5c42c7207cb9cf8c87eda
>> Author: Neil Brown <neilb@notabene.brown>
> ^^^^^^^^^^^^^^^^^^^^
> Grown. I hadn't noticed that. Fixed now I hope.
>
>> Date: Sat Jun 28 08:31:31 2008 +1000
>>
>> Support adding a spare to a live md array with external metadata.
>>
>> i.e. extend the 'md/dev-XXX/slot' attribute so that you can
>> tell a device to fill an vacant slot in an and md array.
>>
>> Signed-off-by: Neil Brown <neilb@suse.de>
>> --- cut ---
>>
>> I have verified that adding this patch to a working 2.6.26 kernel breaks
>> the rebuild/resync
>>
>> I have not verified if reverting it on a 2.6.27 kernel restores the
>> rebuild/resync as it does not revert cleanly...
>>
>> So...
>>
>> Any suggestions of what to try next ?
>
> You mean apart from hitting Neil with a clue-bat?
>
;-)
> Maybe try this patch. I haven't even compile tested it, but I'm
> certain it'll fix your problem.
>
Yeah,
After reading the commit that broke raid10, it's an obvious fix...
And I have now verified it on a 2.6.27.4 kernel that it works!
Thanks!
> Thanks again,
>
> NeilBrown
>
> ----------------------------------------------
> From: NeilBrown <neilb@suse.de>
> Date: Thu, 6 Nov 2008 17:14:31 +1100
> Subject: [PATCH] md: fix bug in raid10 recovery.
>
> Adding a spare to a raid10 doesn't cause recovery to start.
> This is due to an silly type in
> commit 6c2fce2ef6b4821c21b5c42c7207cb9cf8c87eda
> and so is a bug in 2.6.27 and .28-rc.
>
> Thanks to Thomas Backlund for bisecting to find this.
>
> Cc: Thomas Backlund <tmb@mandriva.org>
> Cc: stable@kernel.org
>
> Signed-off-by: NeilBrown <neilb@suse.de>
Tested-by: Thomas Backlund <tmb@mandriva.org>
>
> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
> index da5129a..970a96e 100644
> --- a/drivers/md/raid10.c
> +++ b/drivers/md/raid10.c
> @@ -1137,7 +1137,7 @@ static int raid10_add_disk(mddev_t *mddev, mdk_rdev_t *rdev)
> if (!enough(conf))
> return -EINVAL;
>
> - if (rdev->raid_disk)
> + if (rdev->raid_disk >= 0)
> first = last = rdev->raid_disk;
>
> if (rdev->saved_raid_disk >= 0 &&
--
Thomas
prev parent reply other threads:[~2008-11-06 9:23 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
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 [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=4912B782.2070409@mandriva.org \
--to=tmb@mandriva.org \
--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).