View Single Post
  #5   (View Single Post)  
Old 1st June 2008
TerryP's Avatar
TerryP TerryP is offline
Arp Constable
 
Join Date: May 2008
Location: USofA
Posts: 1,547
Default

Depending on what the real disk size is and assuming it is full, it might be failing to write because some disk space is held back:

Quote:
Originally Posted by tunefs
-m minfree
Specify the percentage of space held back from normal users; the
minimum free space threshold. The default value used is 8%.
Note that lowering the threshold can adversely affect perfor-
mance:

+o Settings of 5% and less force space optimization to always be
used which will greatly increase the overhead for file
writes.

+o The file system's ability to avoid fragmentation will be
reduced when the total free space, including the reserve,
drops below 15%. As free space approaches zero, throughput
can degrade by up to a factor of three over the performance
obtained at a 10% threshold.

If the value is raised above the current usage level, users will
be unable to allocate files until enough files have been deleted
to get under the higher threshold.

Depending on what servers purpose, I'd look at the disk contents as well as the logs.


I remember *twice* having a few hundred megs of core-dumps from php4 causing trouble on a RHEL machine, whose host tried to charge us for more disk space :-)

If it's a mails server, I'd trust people have tight quotas that fit on disk even if everyones full hehe.
__________________
My Journal

Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''.
Reply With Quote