Path: utzoo!utgpu!watserv1!watmath!att!att!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!uokmax!servalan!rmtodd
From: rmtodd@servalan.uucp (Richard Todd)
Newsgroups: comp.unix.sysv386
Subject: Re: File system performance
Message-ID: <1990Nov3.222929.2164@servalan.uucp>
Date: 3 Nov 90 22:29:29 GMT
References: <294@audfax.audiofax.com> <1990Nov3.124110.2155@metro.ucc.su.OZ.AU>
Organization: Ministry of Silly Walks
Lines: 23

dawes@suphys.physics.su.OZ.AU (David Dawes) writes:
>I too am using ESIX rev D with ffs.  One of my file systems became heavily
>fragmented, and got to the point where there were 0 free blocks, and
>5000 free frags.  df reported 10000 blocks free, but attempting to write
>to the file system resulted in "Disk full" errors.  This meant that I
>had an unusable 5MB on a 65MB file system. (BTW, there were plenty of free
>inodes.)

>Is this how FFS is supposed to work, or is there a problem with the ESIX
>implementation?

  Well, that's how FFS works on other machines (I've hit it on Apple Unix
2.0, which includes Berkeley FFS).  Hitting the no-free-blocks limit when
you've got 5M free in fragments is a little unusual; I was hitting the
limit with only ~250K of fragments free on a 282MB filesystem, and on the
(frequent) occasions when the local campus BSD machine fills a partition it
gets down to fairly small values of free-fragment-space (again, in the 
neighborhood of a couple hundred K on ~200MB filesystems).  Evidently you
managed to stumble on a pathological worst-case....
--
Richard Todd	rmtodd@uokmax.ecn.uoknor.edu  rmtodd@chinet.chi.il.us
	rmtodd@servalan.uucp
7 days until the season premiere of WISEGUY!