Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!ctrsol!emory!stiatl!rsiatl!jgd
From: jgd@rsiatl.UUCP (John G. De Armond)
Newsgroups: news.admin
Subject: Re: The Inode-Eating Bug
Message-ID: <282@rsiatl.UUCP>
Date: 8 Oct 89 16:46:06 GMT
References: <906@zorch.SF-Bay.ORG> <231@rsiatl.UUCP> <1989Oct7.213314.17921@twwells.com>
Reply-To: jgd@rsiatl.UUCP (John G. De Armond)
Organization: Radiation Systems, Inc. (a thinktank, motorcycle, car and gun works facility)
Lines: 27

In article <1989Oct7.213314.17921@twwells.com> bill@twwells.com (T. William Wells) writes:
>Apologies, but your scripts do little or nothing to solve the problem.
>
>First: the inode crash can occur regardless of the number of available
>inodes on your system.
>
>Second: the crash can occur almost instantly after you have done a
>fsck, so doing it frequently does not eliminate the problem.
>

Please cite an example of how a crash can occure right after an fsck.
Assuming the file system is not genuinly full or out of inodes.
If the bug works as per what has been posted, my scripts address the
problem rather well.

From a practical perspective, these scripts have reduced the inode problem
on stiatl at my former employer from perhaps twice daily on the news partition
to NEVER. (We were forced to run a tight disk so we are close to the
hairy edge most of the time).  On rsiatl here, the scripts have also
totally eliminated the problem.  That's kinda the bottom line.

John

-- 
John De Armond, WD4OQC                     | Manual? ... What manual ?!? 
Radiation Systems, Inc.     Atlanta, GA    | This is Unix, My son, You 
gatech!stiatl!rsiatl!jgd  **I am the NRA** | just GOTTA Know!!!