On Mon, 5 Nov 2007, Dan Williams wrote:

quoted text
> On 11/4/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>>
>>
>> On Mon, 5 Nov 2007, Neil Brown wrote:
>>
>>> On Sunday November 4, jpiszcz@lucidpixels.com wrote:
>>>> # ps auxww | grep D
>>>> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMA=
ND
quoted text
>>>> root       273  0.0  0.0      0     0 ?        D    Oct21  14:40 [pdfl=
ush]
quoted text
>>>> root       274  0.0  0.0      0     0 ?        D    Oct21  13:00 [pdfl=
ush]
quoted text
>>>>
>>>> After several days/weeks, this is the second time this has happened, w=
hile
quoted text
>>>> doing regular file I/O (decompressing a file), everything on the devic=
e
quoted text
>>>> went into D-state.
>>>
>>> At a guess (I haven't looked closely) I'd say it is the bug that was
>>> meant to be fixed by
>>>
>>> commit 4ae3f847e49e3787eca91bced31f8fd328d50496
>>>
>>> except that patch applied badly and needed to be fixed with
>>> the following patch (not in git yet).
>>> These have been sent to stable@ and should be in the queue for 2.6.23.2
>>>
>>
>> Ah, thanks Neil, will be updating as soon as it is released, thanks.
>>
>
> Are you seeing the same "md thread takes 100% of the CPU" that Jo=EBl is
> reporting?
>

Yes, in another e-mail I posted the top output with md3_raid5 at 100%.

Justin.