# Re: tests/03r5assemV1 issues

- From: Jes Sorensen \<hidden\>
- Date: 2012-07-11 07:18:19 
- List: linux-raid
- Page: https://ratatoskr.run/linux-raid/2012/07/6620999
- Thread: https://ratatoskr.run/linux-raid/2012/07/6620999/t.md

```text
NeilBrown [ref] writes:
> On Fri, 06 Jul 2012 11:59:13 +0200 Jes Sorensen [ref]
> 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
```
