Date: Tue, 03 Apr 2007 18:19:47 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Sean Murphy <smurphy@calarts.edu> Cc: freebsd-questions@freebsd.org Subject: Re: var Filesystem Full Help Message-ID: <46128CB3.2050606@dial.pipex.com> In-Reply-To: <461287EB.4040508@calarts.edu> References: <46127E55.2040005@calarts.edu> <461287EB.4040508@calarts.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46128CB3.2050606>