From owner-freebsd-alpha Sun Feb 17 12:38:57 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 442CD37B400 for ; Sun, 17 Feb 2002 12:38:51 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA10315; Sun, 17 Feb 2002 15:38:50 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g1HKcK218504; Sun, 17 Feb 2002 15:38:20 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15472.5308.590348.105307@grasshopper.cs.duke.edu> Date: Sun, 17 Feb 2002 15:38:20 -0500 (EST) To: Bernd Walter Cc: freebsd-alpha@freebsd.org Subject: Re: runningbufspace deadlock problem on -stable In-Reply-To: <20020217180949.GD42870@cicely8.cicely.de> References: <20020217180949.GD42870@cicely8.cicely.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bernd Walter writes: > I have one -stable production PC164 machine with the problem that > runningbufspace increases over time. <..> > vfs.runningbufspace: 120832 > > The value should return to 0 when the box is IO idle. > > If someone sees this problems on a local machine I would be happy. > I have some patches here adding assertions which I want to avoid > trying on my production machine. I recently had a problem on my workstation. (UP1000, 640MB, 4.5-STABLE, also an NFS server for my various testboxes in my home office). I was doing a local cvs diff on the src/sys tree, as well as building the TGA kernel, and doing a few other things (xemacs, gnome, sawfish, konqueror, 20 or so shells). The cvs diff got wedged in (I think) inode. At this point, I noticed that the FFS node malloc pool seemed to be quite near its limit. I killed the make and tried to recover, but I couldn't seem to get the number of FFS node allocations down & other jobs started to wedge on IO. I was intending to drop into the debugger and get a dump, but the machine locked solid when I tty-switched out of X. I have so far be unable to reproduce the problem. I wonder if these two problems might be related..? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message