From owner-freebsd-current Thu Dec 31 21:22:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02884 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:22:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02877 for ; Thu, 31 Dec 1998 21:22:49 -0800 (PST) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.8.8/8.8.8) with SMTP id XAA15750 for ; Thu, 31 Dec 1998 23:22:27 -0600 (CST) (envelope-from tony@dell.com) Message-Id: <3.0.6.32.19981231232223.00a116a0@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 31 Dec 1998 23:22:23 -0600 To: current@FreeBSD.ORG From: Tony Overfield Subject: processes hanging in "inode" state? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lately, I have been playing with -current on a test system. When I do a "make -j 8 world", everything always works fine with small to moderate amounts of swap usage. When I do a "make -j 32 world", as expected, I encounter a greatly increased amount of swap usage. However, it doesn't ever finish. After a long time, everything simply stops and it cannot start any new programs. If I happen to have top already running, I can switch to it and see numerous processes stuck in the "inode" state. I have no reason to suspect hardware trouble and I think I have plenty of swap space for this to complete, if only it didn't hang. What should I do to find (or help somebody find) the problem? P5/MMX 233MHz, 430FX/PIIX3, 64MB EDO DRAM, 2940U, Quantum/DEC DSP3210. - Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message