Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!decwrl!sun!guy
From: guy@sun.uucp (Guy Harris)
Newsgroups: net.unix
Subject: Re: 4.2BSD Filesystem troubles....
Message-ID: <3157@sun.uucp>
Date: Thu, 16-Jan-86 14:27:54 EST
Article-I.D.: sun.3157
Posted: Thu Jan 16 14:27:54 1986
Date-Received: Sat, 18-Jan-86 01:12:25 EST
References: <12700003@pbear.UUCP>
Organization: Sun Microsystems, Inc.
Lines: 17

> I am working with a vanilla 4.2BSD VAX system, and I have been noticing that
> disk space is vanishing from my filesystems. I have a 45Mb filesystem that
> fsck says has 13Mb free, but df states is full.!!..??? (and can't be
> written to)

4.2BSD reserves a certain percentage of the free space on a file system;
only processes running as superuser can get at that space.  The normal
percentage is 10%, although it's tunable.  The reason for this is that the
block allocation code gets slower when the free space drops below about 10%;
see the paper "A Fast File System for UNIX", in the section "Layout
Policies".  That paper comes with the 4.2BSD documentation.

"fsck" reports the total free space; "df" reports only the free space
available to non-superusers.  (That's why it sometimes reports that a file
system is more than 100% full.)

	Guy Harris