Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 May 1999 15:09:24 -0400 (EDT)
From:      "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com>
To:        graeme@echidna.com (Graeme Tait)
Cc:        freebsd-questions@FreeBSD.ORG, info@boatbooks.com
Subject:   Re: Lost file space
Message-ID:  <199905171909.PAA29513@cc942873-a.ewndsr1.nj.home.com>
In-Reply-To: <37405E48.3EE@echidna.com> from Graeme Tait at "May 17, 99 11:22:00 am"

next in thread | previous in thread | raw e-mail | index | archive | help
[You should really try for < 80 column lines.]

Graeme Tait wrote,
> Recently I noticed that the filesystem listed below is reported "full" while only at 90% 
> capacity (for the df -ik report below, it's almost at "full"). This did not used to be 
> the case AFAIK.
> 
> FWIW, this filesystem was built with 'newfs -f 512 -b 4096 -i 2048', and is mounted 
> 'async local noatime'. In routine operation, there is very little write activity to this 
> filesystem.
> 
> Filesystem  1K-blocks     Used    Avail Capacity iused   ifree  %iused  Mounted on
> 
> /dev/da1s1f   3563104  2941142   336913    90%  908255  733055    55%   /usr/www
> 
> 
> There were a couple of power failures (faulty UPS, wouldn't you know!) and automatic 
> reboots at the colo 20 days ago. I can't say for sure if the problem arose then or 
> later, but I suspect it was later. I'm assuming since the system rebooted OK that the 
> filesystems were clean after the fsck.

That looks exactly right to me,

(3563104 - 2941142 - 336913)/3563104 = 0.0800

The operating system reserves a certain amount of space (8% by
default) because the filesystem performs _much_ better with some free
space available. Performance plumets precipitously after about
10%. However, privileged users may access this extra space. You can
easily fill a fs to 108% when a root owned process goes a little nuts.

To summarize, nothing is broken on your system.

The 8% default can be changed in tunefs(8).

> A question in this connection: the dmesg output stops just before fsck runs towards the 
> end of the boot process - how can you get the fsck output logged?

That should be a very simple hack of the /etc/rc script to log that to
a file.
-- 
Crist J. Clark                           cjclark@home.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905171909.PAA29513>