file system deadlock - the whole story?

Kostik Belousov kostikbel at gmail.com
Wed Jul 19 05:30:33 UTC 2006


On Wed, Jul 19, 2006 at 01:31:17AM -0300, User Freebsd wrote:
> 
> Kostik/Robert ... does this provide enough (any?) information concerning 
> the deadlock situation(s) that are being reported?  is there anything else 
> I should do the next time it happens?
> 
> I tried to submit a GnATs report on this also, but fear that the 
> attachment was a wee bit too big :(
> 
Marc,
thank you for the report. It does contain useful information, I'm looking
into it.

I see at least one obvius deadlock (you shell becomes unresponible when
you tried to make auto-completion, right ?).

> On Tue, 18 Jul 2006, User Freebsd wrote:
> 
> >
> >'k, had a bunch of fun tonight, but one of the results is that I was able 
> >to achieve file system deadlock, or so it appears ...
> >
> >Using the following from DDB:
> >
> >set $lines=0
> >show pcpu
> >show allpcpu
> >ps
> >trace
> >alltrace
> >show locks
> >show alllocks
> >show uma
> >show malloc
> >show lockedvnods
> >call doadump
> >
> >I've been able to produce the attached output, as well as have a core dump 
> >that can hopefully be used to gather any that I may have missed this time 
> >*cross fingers*
> 
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email . scrappy at hub.org                              MSN . scrappy at hub.org
> Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060719/9a19694b/attachment.pgp


More information about the freebsd-stable mailing list