Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!pyramid!uccba!showard
From: showard@uccba.UUCP (Steve Howard)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Wierd 3b inode problem with news.
Message-ID: <1276@uccba.UUCP>
Date: Wed, 11-Nov-87 02:30:17 EST
Article-I.D.: uccba.1276
Posted: Wed Nov 11 02:30:17 1987
Date-Received: Fri, 13-Nov-87 20:36:08 EST
References: <283@paisano.UUCP>
Organization: Univ of Cincinnati, College of Business Admin.
Lines: 14
Keywords: 3b2 inode file system
Summary: Me too....Here is what I found...
Xref: mnetor comp.sys.att:1720 comp.unix.wizards:5422

I have also had this problem with a 3B2 Sys V Rel 2.1.  I found that it would
happen semi-regularly on Monday & Thursday Mornings.  The cron log (which was
usually around 1 MEG (We've got a busy cron :-)) would get /dev/null copied to
it every Mon. & Thurs. morning.  It appears that if we were uncompressing news
and the cronlog got /dev/null cp'd to it at the same time--wham!!!  No more 
inodes!!!  I took the section out of the root crontab that messed with the     
cronlog and everything has lived happily ever after.

Is this caused by the cron writing to the end of a large file as it is
simultaneously deleting it?  Does rnews cause a problem?  Is it purely
coincidence?  Probably, but it hasn't happened on my system since I removed
the section of the crontab that deletes the cronlog.
-- 
Steve Howard      UUCP:  {pyramid,philabs!phri,decuac,mit-eddie}!uccba!showard
U.C. College of Business Administration  USPS:  M.L. 130, Cincinnati, OH 45221