Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!ucsfcgl!cca.ucsf.edu!wet!epsilon
From: epsilon@wet.UUCP (Eric P. Scott)
Newsgroups: news.software.b
Subject: Re: dbz caveat
Summary: Bursting at the seams
Message-ID: <688@wet.UUCP>
Date: 19 Oct 89 04:42:35 GMT
References: <1139@svx.SV.DG.COM> <1989Sep26.223014.13868@ddsw1.MCS.COM> <9668@b-tech.ann-arbor.mi.us> <6512@ficc.uu.net> <9680@b-tech.ann-arbor.mi.us> <1989Oct14.062717.15420@twwells.com> <675@wet.UUCP> <1989Oct16.043012.2938@twwells.com>
Reply-To: epsilon@wet.UUCP (Eric P. Scott)
Organization: Wetware D-D-Diversions, San Francisco
Lines: 16

In article <1989Oct16.043012.2938@twwells.com> bill@twwells.com
	(T. William Wells) writes:
>You can figure that the newsfeed doubles in volume every year. This
>might, now, be an overestimate, but you probably won't go wrong
>making that assumption.

Actually I can.  SVR3 only has 16 bits of inodes!  (I get to use
65488) The best I can do if things get really tight is to split
off comp onto its own filesystem.  Right now I have about 22,000
inodes free (2 weeks, no inet groups).  If you're right, I better
start making "imminent death" predictions.

Hopefully SVR4 will be out before that's necessary.  I really
don't want to drop expiration below 2 weeks.

					-=EPS=-