Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site ccvaxa.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcs!ccvaxa!preece
From: preece@ccvaxa.UUCP
Newsgroups: net.unix-wizards
Subject: Re: UNIX 4.2 thrashing - the cause?
Message-ID: <47500008@ccvaxa.UUCP>
Date: Thu, 24-Jan-85 17:15:00 EST
Article-I.D.: ccvaxa.47500008
Posted: Thu Jan 24 17:15:00 1985
Date-Received: Sat, 26-Jan-85 06:26:24 EST
References: <1282@kaist.UUCP>
Lines: 20
Nf-ID: #R:kaist:-128200:ccvaxa:47500008:000:923
Nf-From: ccvaxa!preece    Jan 24 16:15:00 1985

>	I believe there is a lesson here.  4.2bsd sites should try to keep all
>	filesystems below 90% full (especially those where a great amount of
>	creation and deletion take place daily - /usr, /usr/spool) or suffer
>	degradation.
----------
You don't really have to try very hard to keep your filesystems under 90%
full -- 4.2 will keep normal users from pushing them past that point.
You're missing the fact that the df listing is giving you percentages
relative to a 90% ceiling, NOT relative to total capacity.  Note that
a filesystem shown as 100% full and with 0 blocks available will still
have 10% fewer blocks in the used column than in the capacity column.
Superusers are able to go beyond the 90% limit and df will obediently
report that up to 110% of the filesystem is being used.

Still, it's probably better to try to keep from pushing the 90% (shown
as 100%) level.

scott preece
ihnp4!uiucdcs!ccvaxa!preece