Thanks to everyone on all the ideas they gave me - unfortunately nothing
worked - so when all else fails - reboot!! Once I did this everything is
okay. Here are some of the great ideas everyone gave me:
/: write failed ---> indicate that the "/" (root filesystem) is
the one causing the problem. As you can see with "df" the / filesystem
is the root_domain#root that appear in the listing you put in your
email. It seem it just have 188816/2 KB free.. I divide by 2 because
your listing is in blocks of 512 bytes and not on Kilobytes. You
can issue "df -k" to see a listing in Kilobytes. Well 90 MB of free
space on / could be quite small because some programs use /tmp
as the temporal directory to put temporary data and depending on
the programs your users are running this 90 MB may be too small.
Is it possible that you repartition your hard disk? if not try
making a link of /tmp to /usr/tmp:
# rm /tmp
# ln -s /usr/tmp /tmp
this will make the programs that use /tmp actually use /usr/tmp
instead and then not run out of free space your small "/"
Probably your /tmp is momentarily filled up by something dynamic
Try running fuser/lsof on / and maybe /var as well if it's not a separate
mount point. You can get a situation whereby a process has a lock on a
file even after that file has been deleted. Therefore the filesystem
reports the space as still being in use even though it's actually free.
I think you've run into the BMT exhaustion problem. I'm guessing that
you're running 4.0x, or at least your AdvFS filesystem still is. One
way to find out for sure is go into the / directory, then the .tags
directory, and issue the following command:
# showfile -x M-6
The bottom line will say
extentCnt: xxx
Where the number is probably 683, which means that you are out of
metadata space.
Received on Fri Oct 12 2001 - 17:23:01 NZDT