From: Unix-Admin (Unix-admin@triad.rr.com)
Date: Thu Aug 15 2002 - 22:39:30 EDT
Thanks to all who replied. Almost everyone said that dmesg buffers up a certain quantity of kernel messages; these messages may be old. Since there is no time stamp from dmesg it could have happened 5 minutes or 5 days ago.
Grep the /var/adm/syslog/syslog.log for vx_nospace to see when the error occurred.
One person suggested using du and fuser to get a better picture of file usage.
Check the i-nodes especially if the FS holds a lot of small files.
"df -i" or "bdf -i" on your system. This reports the number of
inodes used - it could be you've run out of those.
The default crontab.root file will empty dmesg buffer periodically:
# log kernel diagnostic messages every 10 minutes
05,15,25,35,45,55 * * * * /usr/sbin/dmesg - >>/var/adm/messages
I tried all of these and right now everything looks okay. I have set up the cron and will keep a close watch.
Thanks again to all that replied.
Tom
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:17 EDT