Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!dscatl!wa4mei!nanovx!techwood!paldn!pwilcox
From: pwilcox@paldn.UUCP (Peter McLeod Wilcox)
Newsgroups: comp.unix.wizards
Subject: System V inode problem
Keywords: inode superblock systemV
Message-ID: <123@paldn.UUCP>
Date: 20 Jul 89 23:47:47 GMT
Sender: news@paldn.UUCP
Organization: Paladin Solutions, Dawsonville GA
Lines: 13

I have run across several ref. to the "infamous System V inode bug",
as someone afflicted with this problem is there a cure?
I am running uPort SysV/386 3.0e, I have a file system dedicated
to news processing and this is where the problem occurs, the superblock
contains an incorrectly low (0) count of the number of free inodes and
must be fixed with fsck.  Currently I seem to have it under control
by running a process which wakes up every minute to make and delete
a file on the problem file system, but it would be nice to have a more
elegant solution, and to know what exactly triggers the error.

Many thanks in advance!
-- 
Pete Wilcox		...gatech!nanovx!techwood!paldn!pwilcox