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

[Andrew Morton <akpm@zip.com.au>]

David Rees wrote:
> 
> On Wed, Aug 29, 2001 at 01:47:47PM -0700, Andrew Morton wrote:
> >
> > 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'.
> 
> OK, here's the ps output:
> 
> # ps xwo pid,command,wchan
>   PID COMMAND          WCHAN
>     1 init [3]         do_select
>     2 [keventd]        context_thread
>     3 [ksoftirqd_CPU0] ksoftirqd
>     4 [kswapd]         kswapd
>     5 [kreclaimd]      kreclaimd
>     6 [bdflush]        raid1_alloc_r1bh
>     7 [kupdated]       log_wait_commit
>     9 [mdrecoveryd]    md_thread
>    10 [raid1d]         md_thread
>    11 [kjournald]      kjournald
>   130 [kjournald]      kjournald
>   131 [kjournald]      wait_on_buffer
>   374 syslogd -m 0     do_select

OK, thanks.  bdflush is stuck in raid1_alloc_r1bh() and
everything else is blocked by it.  I thought we fixed 
that a couple of months ago :(

Could you send the output of `cat /proc/meminfo'?

> 18239 -bash            wait4
> 18274 umount /opt      rwsem_down_write_failed

What are we trying to do here?  Is /opt the deadlocked
filesytem?