Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!ima!minya!jc
From: jc@minya.UUCP
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Wierd 3b inode problem with news.
Message-ID: <413@minya.UUCP>
Date: Wed, 25-Nov-87 21:32:26 EST
Article-I.D.: minya.413
Posted: Wed Nov 25 21:32:26 1987
Date-Received: Sun, 29-Nov-87 02:32:35 EST
References: <283@paisano.UUCP> <156@fesk.UUCP> <3626@islenet.UUCP> <986@edge.UUCP> <993@edge.UUCP>
Organization: home
Lines: 13
Keywords: SysV bugs
Xref: utgpu comp.sys.att:1640 comp.unix.wizards:5227
Summary: How about lost blocks?

While we're working on the out-of-inodes problem, perhaps it should be 
pointed out that there is also a similar out-of-blocks problem.  On this
and quite a lot of other SysV machines, I've been able to cause a file
system to run out of free blocks, in such a way that running fsck finds
a whole lot (typically in the thousands).  I don't have any good evidence
of what causes it, other than that it appears to be similar to the inode
problem:  Running a test program that rapidly creates and unlinks small
files will often produce the problem, especially if you run N copies of
the program in parallel.  I'd work on it here, but I don't have the source
on this machine.  [Well, it's a good excuse to be lazy! :-]

-- 
John Chambers <{adelie,ima,maynard,mit-eddie}!minya!{jc,root}> (617/484-6393)