From owner-freebsd-current Sun Dec 20 13:58:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26062 for freebsd-current-outgoing; Sun, 20 Dec 1998 13:58:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26057 for ; Sun, 20 Dec 1998 13:58:27 -0800 (PST) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (Postfix) with ESMTP id 2E5741E9; Sun, 20 Dec 1998 22:58:20 +0100 (MET) Received: by ariel.xaa.iae.nl (Postfix, from userid 1008) id 694FB3EBE; Sun, 20 Dec 1998 22:58:09 +0100 (CET) Date: Sun, 20 Dec 1998 22:58:09 +0100 From: Mark Huizer To: current@FreeBSD.ORG Subject: current problem -> process hanging on 'inode' state... Message-ID: <19981220225809.A1503@ariel.xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, my fileserver (running Current as of yesterday), is showing weird things, not sure if it's a problem with current or something bad in my fs. anyway: with intensive jobs like tar -cf - /, after a non-deterministic amount of time the process will hang, top showing that it is in the 'inode' blocked queue. Then other processes will start hanging too, making the machine useless. Weird thing: it will go on playing NFS-server without problems. Just starting new programs is impossible, ctrl-alt-del won't work, etc... config: single processor machine, using soft updates, used to run smoothly for weeks, now hangs on most really big disk jobs. Strange enough it seems to survive a make world. Does it ring a bel to anyone? -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message