From owner-freebsd-isp Wed May 10 9:37:36 2000 Delivered-To: freebsd-isp@freebsd.org Received: from larryboy.graphics.cornell.edu (larryboy.graphics.cornell.edu [128.84.247.48]) by hub.freebsd.org (Postfix) with ESMTP id C7A6F37B528; Wed, 10 May 2000 09:37:29 -0700 (PDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Received: from larryboy.graphics.cornell.edu (mkc@localhost) by larryboy.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id MAA79845; Wed, 10 May 2000 12:37:26 -0400 (EDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Message-Id: <200005101637.MAA79845@larryboy.graphics.cornell.edu> To: Joe Karthauser Cc: freebsd-questions@FreeBSD.org, freebsd-isp@FreeBSD.org Subject: Re: 3.0-R server /var running out of inodes (not a usenet question) In-Reply-To: Message from Joe Karthauser of "Wed, 10 May 2000 17:04:28 BST." <20000510170428.M21249@pavilion.net> Date: Wed, 10 May 2000 12:37:26 -0400 From: Mitch Collinsworth Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >What have you got that creates lots and lots of little files every now >and then, maybe in /var/tmp ? Lots and lots, as in half a million. Excellent question. My original message gave the list of work being done by this machine: >I have a server running 3.0-R that serves DNS, ntp, >NIS, NFS, sendmail, imap, pop, majordomo, DHCP, and syslog. I'm not imagining any of these going to that extreme under normal operation. Maybe sendmail or majordomo if they were under extreme load, but they're not. If they were there would be evidence of that in the logs. I believe it's got to be a failure mode of some sort. Especially since this seems to happen rather suddenly and then all traces are gone after reboot. Seems like a race condition somewhere. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message