var Filesystem Full Help

Alex Zbyslaw xfb52 at dial.pipex.com
Tue Apr 3 17:19:50 UTC 2007


Sean Murphy wrote:

>> Check df -i as you may have run out of inodes rather than out of file 
>> space.
>
>
> Looks as though I have plenty of inodes
>
> muse2# df -i
> Filesystem    1K-blocks    Used     Avail Capacity iused    ifree 
> %iused  Mounted on
> /dev/amrd0s1a   1012974   57694    874244     6%    1520   139790    
> 1%   /
> devfs                 1       1         0   100%       0        0  
> 100%   /dev
> /dev/amrd0s1e   1012974   33192    898746     4%   11141   130169    
> 8%   /tmp
> /dev/amrd0s1f   9938894 4368142   4775642    48%  279371  1015987   
> 22%   /usr
> /dev/amrd0s1g 257098734 9794488 226736348     4%  113153 33118717    
> 0%   /usr/home
> /dev/amrd0s1d   2026030  510498   1353450    27%     866   281756    
> 0%   /var
> muse2#

[...]

> Apr  3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 
> 126291 on /var: filesystem full

I've no idea what mimedefang does.  Is it possible it is trying to 
create a file which is larger than your available disk space?  If it did 
that then deleted the offending file, then df would look normal except 
at the point where mimedefang was creating the enormous file.

If it happens frequently, then you could just run df in a loop and read 
back through

for tcsh

while (1)
df -h
echo ""
sleep 1
end

Hit ^C when you've seen enough.  You could redirect df and echo e.g. >> 
/tmp/DF to put output in a file  or even | tee -a /tmp/DF to put to a 
file and see on screen.

--Alex




More information about the freebsd-questions mailing list