NFS deadlock on 9.2-Beta1

Konstantin Belousov kostikbel at gmail.com
Sun Jul 28 06:25:57 UTC 2013


On Sat, Jul 27, 2013 at 03:13:05PM -0700, Michael Tratz wrote:
> Let's assume the pid which started the deadlock is 14001 (it will be a different pid when we get the results, because the machine has been restarted)
> 
> I type:
> 
> show proc 14001
> 
> I get the thread numbers from that output and type:
> 
> show thread xxxxx
> 
> for each one.
> 
> And a trace for each thread with the command?
> 
> tr xxxx
> 
> Anything else I should try to get or do? Or is that not the data at all you are looking for?
> 
Yes, everything else which is listed in the 'debugging deadlocks' page
must be provided, otherwise the deadlock cannot be tracked.

The investigator should be able to see the whole deadlock chain (loop)
to make any useful advance.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20130728/da4fb718/attachment.sig>


More information about the freebsd-stable mailing list