From owner-freebsd-questions Mon May 17 12: 9:12 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 75CD314CD0 for ; Mon, 17 May 1999 12:09:08 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id PAA29513; Mon, 17 May 1999 15:09:24 -0400 (EDT) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199905171909.PAA29513@cc942873-a.ewndsr1.nj.home.com> Subject: Re: Lost file space In-Reply-To: <37405E48.3EE@echidna.com> from Graeme Tait at "May 17, 99 11:22:00 am" To: graeme@echidna.com (Graeme Tait) Date: Mon, 17 May 1999 15:09:24 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG, info@boatbooks.com Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [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