🚀 go-pugleaf

Have the following hardware and OS:
	Balance B8 with Dynix 3.1.2

I've looked over the man pages for tunefs and newfs, and scanned
through the document about the BSD Fast File system in Vol. II of the
manuals, but I'm not real clear on what exactly is going on with this
free space being reserved.  According to the article about the FFS it
says something to the effect that having 10% free space makes things
work better and faster--how and why is this?  What happens when you
cut this down to about 5% or 2% or nothing at all? 

I've also noticed that when using newfs if I specify a value less than
10 to its -m option I get a warning message about "space optimazation"
is being used because less than 10% free.  What exactly does this mean?
What are the ramifications of initially creating a filesystem with
less than 10% free and this "space optimzation" in effect and then
later bumping it up to 10 or better via tunefs?  Does this in itself
cause the filesystem to stop using "space optimzation" and start using
whatever is more effecient?

Note, I get the general idea that having 10% makes things better, and
is the way one should normally create their filesystems, I
just want to understand why and what the situations are that arise
when it is less than 10% and for that matter more than 10%.

Thanks.
-- 

+--------------------+-------------------------------------------------------+
|   Michael Faurot   | Domain: mfaurot@bogart.UUCP		             |
|   ------- ------   | UUCP:   ...uunet!media!ka3ovk!irscscm!bogart!mfaurot  |
+--------------------+-------------------------------------------------------+