From owner-freebsd-questions Tue Jan 28 8:37:35 2003 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 0419B37B4C0 for ; Tue, 28 Jan 2003 08:37:29 -0800 (PST) Received: from moroni.pp.asu.edu (moroni.pp.asu.edu [129.219.120.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4CD643F43 for ; Tue, 28 Jan 2003 08:37:25 -0800 (PST) (envelope-from iddwb@moroni.pp.asu.edu) Received: (from iddwb@localhost) by moroni.pp.asu.edu (8.11.6/8.11.6) id h0SGbLD26661 for freebsd-questions@freebsd.org; Tue, 28 Jan 2003 09:37:21 -0700 Date: Tue, 28 Jan 2003 09:37:20 -0700 From: David Bear To: freebsd-questions@freebsd.org Subject: syslog message wrt inodes Message-ID: <20030128093720.A26639@asu.edu> Reply-To: David.Bear@asu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm getting messages like below that I'm out of inodes on /var. asu.edu kernel log messages: >id 25 on /var: out of inodes > syslogd: /var/log/auth.log: No such file or directory > syslogd: /var/log/maillog: No such file or directory > syslogd: /var/log/cron: No such file or directory > syslogd: /var/log/auth.log: No such file or directory > syslogd: /var/log/maillog: No such file or directory > syslogd: /var/log/cron: No such file or directory > syslogd: /var/log/auth.log: No such file or directory > syslogd: /var/log/maillog: No such file or directory > syslogd: /var/log/cron: No such file or directory > syslogd: /var/log/auth.log: No such file or directory > syslogd: /var/log/maillog: No such file or directory > syslogd: /var/log/cron: No such file or directory Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/ad0s1a 128990 37232 81440 31% 1316 14938 8% / /dev/ad0s1f 257998 4 237356 0% 2 32508 0% /tmp /dev/ad0s1g 2341102 508366 1645448 24% 37711 256175 13% /usr /dev/ad0s1e 257998 25572 211788 11% 8298 24212 26% /var procfs 4 4 0 100% 25 507 5% /proc Last week my var volume did run out of inodes. I erase some snort logs to free up the inodes. But it appears the kernel or syslogd doesn't know about it. any pointers on letting the kernel know I have enough inodes? -- David Bear College of Public Programs/ASU Mail Code 0803 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message