Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site isucs1.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!ihnp4!stolaf!umn-cs!isucs1!notes From: notes@isucs1.UUCP Newsgroups: net.unix-wizards Subject: Squashed Inodes on 4.2 Message-ID: <203@isucs1.UUCP> Date: Mon, 29-Oct-84 15:09:58 EST Article-I.D.: isucs1.203 Posted: Mon Oct 29 15:09:58 1984 Date-Received: Wed, 31-Oct-84 00:30:14 EST Sender: notes@isucs1.UUCP Organization: Iowa State University Lines: 61 Nf-ID: #N:isucs1:18100003:000:2008 Nf-From: isucs1!root Oct 29 14:05:00 1984 After having several crashes in the area of _iget() in the kernel, I did a pstat on the inode list. We seem to accumulate inodes with very large reference counts. Apparantly the inode count is being decremented past zero. These inodes sometimes have their links messed up and that is what causes the system to crash. Does anybody else have this problem and is there a fix? We are running 4.2BSD on a VAX 11/730, but I have also seen the bad inodes on a VAX 11/780 running 4.2BSD. Pstat reports the link count to be 255, but it is actually 65535 as pstat trucates to byte size for output. % pstat -i 68/212 active inodes LOC FLAGS CNT DEVICE RDC WRC INO MODE NLK UID SIZE/DEV 80103540 24 11, 0 0 0 2 41ed 15 0 1024 80103690 T 1 11, 0 0 0 41 81ed 1 0 13312 (Intervening entries deleted) 80105a00 255 11, 7 0 0 16379 41ed 2 6 512 (Intervening entries deleted) After seeing this from pstat, I used adb to look at the inode. Adb reports that the count is negative(rolled over). % adb -k /vmunix /dev/mem sbr 80022c64 slr 19dc p0br 802a9200 p0lr c4 p1br 7faa9600 p1lr 1ffff2 80105a00$