Re: kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?)

Andrew Morton
2001-08-29T20:47:56Z

David Rees wrote:
>
> ...
> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
> root 1 0.0 0.0 1368 72 ? S Aug27 0:05 init [3]
> root 2 0.0 0.0 0 0 ? SW Aug27 0:00 [keventd]
> root 3 0.0 0.0 0 0 ? SWN Aug27 0:00 [ksoftirqd_CPU0]
> root 4 0.0 0.0 0 0 ? SW Aug27 0:03 [kswapd]
> root 5 0.0 0.0 0 0 ? SW Aug27 0:00 [kreclaimd]
> root 6 0.0 0.0 0 0 ? DW Aug27 0:00 [bdflush]
> root 7 0.0 0.0 0 0 ? DW Aug27 0:00 [kupdated]
> root 9 0.0 0.0 0 0 ? SW< Aug27 0:00 [mdrecoveryd]
> root 10 0.0 0.0 0 0 ? SW< Aug27 0:00 [raid1d]
> root 11 0.0 0.0 0 0 ? SW Aug27 0:02 [kjournald]
> root 130 0.0 0.0 0 0 ? SW Aug27 0:00 [kjournald]
> root 131 0.0 0.0 0 0 ? DW Aug27 0:01 [kjournald]
> root 374 0.0 0.0 1428 176 ? S Aug27 0:00 syslogd -m 0
> root 379 0.0 0.0 1984 396 ? S Aug27 0:00 klogd -2
> [sybase@zorro ~]$
>
> As you can see, bdflush, kupdated and kjournald appear to be deadlocked.
>

Certainly seems that way.

Can you please send the output of

ps xwo pid,command,wchan

Also, try a SYSRQ-T and, if the result makes it into the
logs, please pass it through `ksymoops -m System.map'.

Thanks.

-