Date: Wed, 19 Jul 2006 01:31:17 -0300 (ADT) From: User Freebsd <freebsd@hub.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: Robert Watson <rwatson@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: file system deadlock - the whole story? Message-ID: <20060719012941.H1799@ganymede.hub.org> In-Reply-To: <20060718074804.W1799@ganymede.hub.org> References: <E1FxzUU-000MMw-5m@cs1.cs.huji.ac.il> <20060705100403.Y80381@fledge.watson.org> <cone.1152136419.991036.72616.1000@zoraida.natserv.net> <20060705234514.I70011@fledge.watson.org> <20060715000351.U1799@ganymede.hub.org> <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> <20060718074804.W1799@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :( 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@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060719012941.H1799>