Re: The read and write timeouts story, next stage...

[Teemu Rinta-aho <teemu%rinta-aho.org@localhost>]

On Dec 21, 2009, at 11:22 PM, Teemu Rinta-aho wrote:

>> root. Then by either building a NetBSD release or causing the
>> raidframe to do parity check (by e.g. pressing the reset button)
>> I can reproduce the problem.
> 
> It seems not any more. Now the parity re-write happens in under a minute.
> Wonder what has happened? If I follow the process with 'raidctl -S raid0'
> I see ETA first being around 1:30, then dropping to 0:30 and then quickly
> being finished. In general this is very nice but how can I force raidframe
> to really go through the whole RAID set?

To be more precise, a kernel compiled from 5.0_STABLE on Aug 4th
does the parity checking without jumping directly to the end.. So
something has changed in the raidframe code?

Teemu