From owner-freebsd-questions@FreeBSD.ORG Thu Jul 24 21:59:17 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3538937B401 for ; Thu, 24 Jul 2003 21:59:17 -0700 (PDT) Received: from web1.nexusinternetsolutions.net (web1.nexusinternetsolutions.net [206.47.131.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 3C81A43F3F for ; Thu, 24 Jul 2003 21:59:14 -0700 (PDT) (envelope-from dave@hawk-systems.com) Received: (qmail 2840 invoked from network); 25 Jul 2003 04:59:12 -0000 Received: from unknown (HELO ws1) (65.49.236.97) by web1.nexusinternetsolutions.net with SMTP; 25 Jul 2003 04:59:12 -0000 From: "Dave [Hawk-Systems]" To: Date: Fri, 25 Jul 2003 00:59:11 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: file table is full - but not...? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 04:59:17 -0000 received the following from a logcheck; Unusual System Events =-=-=-=-=-=-=-=-=-=-= Jul 24 23:11:50 web1 /kernel: le: table is full Jul 24 23:11:50 web1 /kernel: file: table is full Jul 24 23:14:00 web1 /kernel: le: table is full Jul 24 23:14:00 web1 /kernel: file: table is full Jul 24 23:14:00 web1 /kernel: pid 94326 (cron), uid 0: exited on signal 11 (core dumped) Jul 24 23:14:07 web1 /kernel: file: table is full Jul 24 23:14:07 web1 /kernel: pid 93772 (httpd), uid 65534: exited on signal 11 Jul 24 23:14:07 web1 /kernel: file: table is full in a bit of a panic I logged into the server and checked the file table > df -ki Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/ad0s1a 99183 35681 55568 39% 1401 23685 6% / /dev/ad0s1f 55177478 5942572 44820708 12% 271618 13521148 2% /usr /dev/ad0s1e 19815 507 17723 3% 148 4906 3% /var /dev/ad1s1e 56824822 6443295 45835542 12% 2033 14203405 0% /backup procfs 4 4 0 100% 276 768 26% /proc while that was about 35 min after the incident, nothing should be even close to maxing out and causing that error... any ideas? Dave