pwilcox@paldn.UUCP (Peter McLeod Wilcox) (07/21/89)
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
randall@uvaarpa.virginia.edu (Randall Atkinson) (07/27/89)
The inode problem was resolved in a later version of your OS. You indicated that you are running Microport System V/386 3.0. The inode problem is no longer present in AT&T System V/386 Release 3.2u and later (and the equivalent versions from BellTech, Interactive, SCO, etc.). The real solution is to upgrade your OS version, though whether Microport is still running I don't know.