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 [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
