From owner-freebsd-fs Fri Jun 25 3:34:12 1999 Delivered-To: freebsd-fs@freebsd.org Received: from gera.nix.nns.ru (ns.nns.ru [194.135.102.10]) by hub.freebsd.org (Postfix) with ESMTP id 2ADAA154E7 for ; Fri, 25 Jun 1999 03:34:08 -0700 (PDT) (envelope-from dflit@nns.ru) Received: (from dflit@localhost) by gera.nix.nns.ru (8.9.1a/8.7.3) id OAA25999 for freebsd-fs@freebsd.org; Fri, 25 Jun 1999 14:34:07 +0400 (MSD) To: freebsd-fs@freebsd.org Message-ID: Organization: National Electronic Library Date: Fri, 25 Jun 1999 14:34:07 +0400 (MSD) X-Mailer: Mail/@ [v2.45 FreeBSD] From: Dmitry Flitmann Reply-To: dflit@nns.ru Error-to: dflit@nns.ru Subject: Xeon box hanging, top shows "FFS_node". FFS problem? Lines: 31 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there! We've got a "fast" computer for our database (Intel SC450NX, 2xXeon/500MHz, 1G RAM, SymBios U2W SCSI onboard, 2xPCI, 3x18G Seagate Cheetah, OS - FreeBSD 3.2-R). At first, we had to patch NCR driver - then it worked fine for some time. When we started to load our new server with data (1 process creating about 50 small files in a second), a strange effect appears - system ~hangs, it does not create any new processes anymore. When we have "top" running at that moment, we can see that main process (which creates files) has state "FFS_node". Our first idea was that the problem is in a patched ncr driver, so we have replaced SymBios with Adaptec 2940U2W, but effect persists. CPU load is not very high, there are not a lot of processes, and no one keeps a lot of files open simultaneously. Is it a problem in FFS implementation? Or, maybe, some kernel option can help? sorry for poor English. Sincerely, Dmitry Flitman National News Service/National Electronic Library. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message