<div>
First thing that comes to mind is lsof.. <a href="http://freshmeat.net/projects/lsof/" rel="ugc">http://freshmeat.net/projects/lsof/</a><br />
<br />
I havent used it myself, but to quote from them:-<br />
<br />
&quot;Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open Files, and it does just that. It lists information about any files that are open by processes currently running on the system. It can also list communications open by each process.&quot;<br />
<br />
Sounds like what you want..
</div>


<div>
note that FreeBSD keeps a certain amount of space reserved for the root user (I believe it's 5% or 10%) so that you might see a filesystem/partition go above 100% utilization ...that means you're really absolutely completely full on that partition/fs. Do a df -h and see which FS's are full. You may want to empty some space if you can and consider doing a &quot;make distclean&quot; in /usr/ports if you haven't in a while.
</div>


<div>
<br />
<br />
Actually the / partition was 102% usage, but after reboot and fsck'ed, it turned into 12% usage again...<br />
<br />
That's what is quite weird
</div>


<div>
That is not weird - you deleted an open file, and process kept it open and continued to write to it.<br />
<br />
lsof -n | grep VCHR | grep -v /<br />
will show offender process.
</div>


<div>
Sorry for the late reply.<br />
<br />
I've been waiting for the situation to reproduce again. Actually it's happening, and tried to see if there was an open file being deleted like gheist suggested, however seems that's not the cause.<br />
<br />
Once it starts in about 2 hours it fills the 73G drive from it's normal usage of 12%.<br />
<br />
Any ideas about?
</div>


<div>
<br />
Another interesting thing is that, running du or rurep on / with -x option, it reports 7.1 G usage.<br />
<br />
I just wonder how does df determines the disk usage and how does du or durep.<br />
<br />
May be there's some port able of determining and list the usage in the same way df does?
</div>


<div>
What does mount -v tell about that mount point in question ???
</div>


<div>
We need to know more about what your partition structure looks like and which partition is filling. &nbsp;in the intial question you said it was your root partition filling, but then in a later comment you said an entire 73G drive is filling.<br />
<br />
What are your partitions, how big are they, what filesystems do they use, and which ones are filling?<br />
<br />
In PARTICULAR, if it's your / partition that's filling up - do you have a separate partition for /tmp?
</div>


<div>
# mount -v<br />
/dev/amrd0s1a on / (ufs, local, soft-updates, writes: sync 15794 async 2149728, reads: sync 53777 async 13404)<br />
/dev/amrd1s1a on /www (ufs, local, soft-updates, writes: sync 63 async 160024, reads: sync 2018448 async 2185387)<br />
procfs on /proc (procfs, local)<br />
<br />
<br />
# df<br />
Filesystem &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1K-blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp;Mounted on<br />
/dev/amrd0s1a &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;70469488 &nbsp;65424488 &nbsp; -592556 &nbsp; 101% &nbsp; &nbsp;/<br />
/dev/amrd1s1a &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 567892762 278256984 244204358 &nbsp; &nbsp;53% &nbsp; &nbsp;/www<br />
procfs &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;4 &nbsp; &nbsp; &nbsp; &nbsp; 4 &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; 100% &nbsp; &nbsp;/proc<br />
<br />
<br />
# df -i<br />
Filesystem &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1K-blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on<br />
/dev/amrd0s1a &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;70469488 &nbsp;65425472 &nbsp; -593540 &nbsp; 101% &nbsp;225884 &nbsp; 4195234 &nbsp; &nbsp;5% &nbsp; /<br />
/dev/amrd1s1a &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 567892762 278258144 244203198 &nbsp; &nbsp;53% 1429259 140886515 &nbsp; &nbsp;1% &nbsp; /www<br />
procfs &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;4 &nbsp; &nbsp; &nbsp; &nbsp; 4 &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; 100% &nbsp; &nbsp; 247 &nbsp; &nbsp; &nbsp;3869 &nbsp; &nbsp;6% &nbsp; /proc<br />
<br />
<br />
Actually the drive that gets filled is mounted on /, the web server files are in a raid 0 of 2x300GB SCSI drives.<br />
<br />
<br />

</div>


<div>
<br />
Actually I was looking at apache server error log and noticed quite amount of lines like:<br />
<br />
[Fri Jul 22 07:12:19 2005] [notice] child pid 73132 exit signal Segmentation fault (11)<br />
<br />
I don't if this may be cause for the drive being completelly full right now, but I remember some time ago having such error messages in another box and finally the culprit was the ram chips...<br />
<br />
Any thougths about?
</div>


<div>
have you tried booting to single user mode and fsck'ing the root filesystem?
</div>


<div>
Hello,<br />
<br />
thanks to all for the valuable tips. I reckon the partitioning scheme for that box was not the best being demostrated the issues caused on that filling issues.<br />
<br />
Actually I have disabled cronolog piperd log rotation for all sites temorarily and only left working the error log to determine if that was the cause, and after some days, it appears that this log rotation was the cause.<br />
<br />
I wonder why it was causing issues in this server, as actually the log rotation method is being used in the rest of servers without causing any issues (and worked for months correctly before started to behave like that).<br />
<br />
Also don't know why the suggested command from gheist &quot;lsof -n | grep VCHR | grep -v /&quot; was not showing any files at all during the issue... Any idea about?<br />
<br />
Thanks All,<br />
DemienX.
</div>


<div>
Because your disk is fscking full ..... with data.<br />
<br />
The problem I mentioned happens when multiple admins do not coordinate what they do or unskilled users delete their open files.<br />

</div>


<div>
Have you tried doing df -hd 1 when you have the problem? &nbsp;That would tell you for sure where the majority of the dreck was congealing.<br />
<br />
Note: it is very possible to simply migrate this install to a new and betterly-partitioned drive without losing anything. &nbsp;All you have to do is set up proper partitions, give the drive a normal MBR, and then do cp -Rpv from the directories on the old drive to each of the partitions on the new, and presto, you're good to go.
</div>


<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
actually one FreeBSD 4.10 machine is reporting a negative value for available disk space on /.<br />
<br />
Being told that this may be caused by some scripts not properly closing open file handles,<br />
is there any was I can monitor the actual open files for writting or better way to find the cause of this weird report?<br />
<br />
Thanks in advance!
</div>
</div>


Hello,

actually one FreeBSD 4.10 machine is reporting a negative value for available disk space on /.

Being told that this may be caused by some scripts not properly closing open file handles,
is there any was I can monitor the actual open files for writting or better way to find the cause of this weird report?

Thanks in advance!

Negative value for available disk space

Unix is a multitasking, multi-user computer operating system originally developed in 1969 at Bell Labs. Today, it is a modern OS with many commercial flavors and licensees, including FreeBSD, Hewlett-Packard’s UX, IBM AIX and Apple Mac OS-X. Apart from its command-line interface, most UNIX variations support the standardized X Window System for GUIs, with the exception of the Mac OS, which uses a proprietary system.