From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: tests/03r5assemV1 issues
Date: Wed, 11 Jul 2012 09:18:19 +0200 [thread overview]
Message-ID: <wrfjr4sisr44.fsf@redhat.com> (raw)
In-Reply-To: <20120711142053.36d33f61@notabene.brown> (NeilBrown's message of "Wed, 11 Jul 2012 14:20:53 +1000")
NeilBrown <neilb@suse.de> writes:
> On Fri, 06 Jul 2012 11:59:13 +0200 Jes Sorensen <Jes.Sorensen@redhat.com>
> wrote:
>> Hi Neil,
>>
>> Odd - I see it with
>> mdadm: 721b662b5b33830090c220bbb04bf1904d4b7eed
>> kernel: ca24a145573124732152daff105ba68cc9a2b545
>>
>> I've seen this happen for a while fwiw.
>>
>> Note the box has a number of external drives with a number of my scratch
>> raid arrays on it. It shouldn't affect this, but just in case.
>>
>> The system installed mdadm is a 3.2.3 derivative, but I checked running
>> with PATH=. as well.
>
> Thanks.
> I think I figured out what is happening.
>
> It seems that setting the max_speed down to 1000 is often enough, but not
> always. So we need to set it lower.
> But setting max_speed lowers is not effective unless you also set min_speed
> lower. This is the tricky bit that took me way too long to realised.
>
> So with this patch, it is quite reliable.
Hi Neil,
Just tried it out here, and it does indeed solve the problem for
me. Makes sense in the end :)
Looks like we need the same fix in tests/07reshape5intr
Thanks for figuring this out.
Cheers,
Jes
prev parent reply other threads:[~2012-07-11 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 13:24 tests/03r5assemV1 issues Jes Sorensen
2012-07-03 1:44 ` NeilBrown
2012-07-03 16:07 ` Jes Sorensen
2012-07-04 5:23 ` NeilBrown
2012-07-06 9:59 ` Jes Sorensen
2012-07-11 4:20 ` NeilBrown
2012-07-11 4:28 ` Roman Mamedov
2012-07-11 7:18 ` Jes Sorensen [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=wrfjr4sisr44.fsf@redhat.com \
--to=jes.sorensen@redhat.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.