Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!adm!bzs@bu-cs.bu.EDU
From: bzs@bu-cs.bu.EDU (Barry Shein)
Newsgroups: comp.unix.wizards
Subject: RFS - losing disk free space count
Message-ID: <2041@brl-adm.ARPA>
Date: Sat, 27-Dec-86 13:40:58 EST
Article-I.D.: brl-adm.2041
Posted: Sat Dec 27 13:40:58 1986
Date-Received: Sat, 27-Dec-86 20:42:00 EST
Sender: news@brl-adm.ARPA
Lines: 29


From: "Shawn F. Mckay" 
>When the whole thing started I had about
>600 blocks free on /dev/ra0a. (My root partition). But I soon got messages
>saying I was out of space. In fact, doing a df show'd me being at 102%, 0
>free.

4.x (x>1) reserves 10% (actually, it's settable, but that's the default) of
the disk. Thus you can have a disk up to 110% full. The reason is that the
disk block allocation routines start to slow down excessively with more than
90% of the disk full. The super-user is allowed to allocate this last 10%.

Is this what is causing your "problem"? It's not a bug, it's a...

The fact that you got errors at 102% could be caused by a number of things:

	a) If you were the super-user the other 8% might have been
	eaten up by a tmp file but released when the compile failed
	(ie. before you got a chance to do a 'df'.)

	b) If you weren't root something else was eating blocks
	while you were working, you were denied @100% but some other
	process ate the 2% (I dunno, a print spooler or mail daemon?)
	by the time you did a 'df'.

Solution: free up some disk space on root (c'mon do you really need that
oovmunix and /etc/termcap.orig file :-) or work on another disk.

	-Barry Shein, Boston University