[609] in arla-drinkers
Re: Another debug run with the arla lockup problem
daemon@ATHENA.MIT.EDU (Magnus Ahltorp)
Wed Feb 17 13:11:04 1999
From owner-arla-drinkers@stacken.kth.se Wed Feb 17 18:11:03 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 2945 invoked from network); 17 Feb 1999 18:11:02 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 17 Feb 1999 18:11:02 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id TAA18033
for arla-drinkers-list; Wed, 17 Feb 1999 19:05:09 +0100 (MET)
Received: from turbot.pdc.kth.se (turbot.pdc.kth.se [130.237.221.42])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id TAA18029
for <arla-drinkers@stacken.kth.se>; Wed, 17 Feb 1999 19:05:02 +0100 (MET)
Received: (from d95-mah@localhost)
by turbot.pdc.kth.se (8.8.7/8.8.7) id TAA27097;
Wed, 17 Feb 1999 19:04:42 +0100 (MET)
To: "Neulinger, Nathan R." <nneul@umr.edu>
Cc: <arla-drinkers@stacken.kth.se>
Subject: Re: Another debug run with the arla lockup problem
References: <9DA8D24B915BD1118911006094516EAF019C7F19@umr-mail02.cc.umr.edu>
From: Magnus Ahltorp <map@stacken.kth.se>
Date: 17 Feb 1999 19:04:42 +0100
In-Reply-To: "Neulinger, Nathan R."'s message of "Wed, 17 Feb 1999 11:11:01 -0600"
Message-ID: <ixdn22cnbyd.fsf@turbot.pdc.kth.se>
Lines: 20
X-Mailer: Gnus v5.6.45/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
> As indicated in the debug trace
> (http://www.umr.edu/~nneul/debug-traces/arla-webindex-19990217.gz), arla
> seems to get into a state where it spins doing getnode/installnode with no
> xfs logging activity. That is around line 1000 of the log. It looks like the
> last xfs activity taking place is an xfs_node_find.
Are you sure that klogd is still alive? I have had problems with klogd
dying when heavily loaded. Arla's debug output suggests that there is
an xfs talking to it.
> Oh, BTW, something else - on this machine if I leave it running, at some
> point it seems to get into a state where it spins doing clear_all_childs.
> (Can't get into it to get the debug output and console spinning too fast to
> get any more details.)
Does this spinning never stop? If it stops, it's probably just normal
invalidation.
/Magnus
map@stacken.kth.se
