Kirk McKusick e50342e665 Yesterday I had to fix a badly broken disk, and found that fsck kept dying: ... DIR I=64512 CONNECTED. PARENT WAS I=4032 fsck: cannot find inode 995904 fsdb found the inodes with no problem: fsdb (inum: 64512)> inode 995904 current inode: directory I=995904 MODE=40777 SIZE=512 MTIME=Feb 14 15:27:07 2000 [0 nsec] CTIME=Feb 14 15:27:07 2000 [0 nsec] ATIME=Feb 24 10:31:58 2000 [0 nsec] OWNER=nobody GRP=nobody LINKCNT=4 FLAGS=0 BLKCNT=2 GEN=38a41386 Direct blocks: 8094568 0 0 0 0 0 0 0 0 0 0 0 Indirect blocks: 0 0 0 The problem turns out to be a program logic error in fsck. It stores directory inodes internally in hash lists, using the number of directories to form the hash key: inpp = &inphead[inumber % numdirs]; Elsewhere, however, it increments numdirs when it finds unattached directories. I've made the following fix, which solved the problem in the case in hand. Submitted by: Greg Lehey <grog@lemis.com> Reviewed by: Matthew Dillon <dillon@apollo.backplane.com> Approved by: Kirk McKusick <mckusick@mckusick.com>		2000-02-28 20:02:41 +00:00
..
SMM.doc
dir.c
fsck.8
fsck.h	Yesterday I had to fix a badly broken disk, and found that fsck kept dying:	2000-02-28 20:02:41 +00:00
inode.c	Yesterday I had to fix a badly broken disk, and found that fsck kept dying:	2000-02-28 20:02:41 +00:00
main.c	Fix the use of an uninitialized variable in the previous commit.	2000-01-10 14:20:53 +00:00
Makefile
pass1.c
pass1b.c
pass2.c
pass3.c
pass4.c
pass5.c
preen.c
setup.c	Yesterday I had to fix a badly broken disk, and found that fsck kept dying:	2000-02-28 20:02:41 +00:00
utilities.c