[OpenAFS-devel] Any tips for tracking down causes of hangs?

[Nickolai Zeldovich]

> Is there any straightforward way to see what a particular process is
> hung against as far as afsd is concerned?

On Solaris, this is really easy: you find the struct proc for the
hung process, and look at the stack trace starting at tlist->sp. :)
Probably kgdb lets you do similar things on Linux.  You might try
using cmdebug remotely, if the in-kernel Rx server is still working;
this sounds like a deadlock of some sort, which should show up in
cmdebug output in some way.  You could also enable lock tracing, in
which case your fstrace output should tell you where the deadlock
occurred (assuming you can usefully run fstrace).

-- kolya