KEN%ORION.BITNET@CUNYVM.CUNY.EDU (Kenneth Ng) (12/02/87)
I maintain news on an AT&T 3b15 running System 5.2.2 and have also noticed the inode problem. I've never been able to figure out why it occurs but I've noticed the following: If it happens, reboot the system, if you just umount, fsck, and then mount it will probably happen again within a day. If it happens twice, remake the filesystem with a different number of inodes. For some reason different number of inodes will change the frequency of the problem. No correlation has yet been found.