Kernel panic: EXT2-fs panic (device 08:03): ext2_read_inode: bad inode number: 0
This is my /usr partition. This almost always happens during heavy SCSI
bus activity (often at 2AM when the incremental backup starts) Its
happened with 2.0.31pre5,6,7 and 2.0.30 & 29. I believe it started
somewhere in the 2.0.2x series. I am downloading those kernels now in an
effort to find out. It happens every few days. I searched dejanews for
this message and found one post with a kernel patch. That patch looked
to be incorporated in the 2.0.30 kernel so I upgraded from 2.0.29. It
seemed that the frequency went down to every few weeks at that point.
However the problem was worsened by my recently consolidating my
fulltime PPP connection and UUCP connections to this machine. It also
gets a small (100Mb/day) newsfeed.
This is a 486-66 VLB with a buslogic BT445S controller, HP 2Gb disk and
DAT tape, 32Mb parity RAM, WD8013 ethernet.
I never see any other error messages. I ran badblocks without error. I
made it happen in a few minutes with 10 simultaneous 10Mb bonnies. The
second time I tried that (after a reboot) the machine locked up solid
(no disk activity)
1) Can I supply more info to help track this down? Is it possibly a
hardware problem? (the message is always exactly the same) Any
particular kernel version to try?
2) How can I make the machine reboot when this happens? Regardless of
/proc/sys/kernel/panic the machine never reboots by itself. In fact all
attempts at soft rebooting fail. df, shutdown, sync, telinit and
ctl-alt-del all hang. My usual method is to kill crond, pppd and inn (in
an effort to close as many open files as possible) and then hit the
reset button. Do I need to use the software watchdog to force a reboot?
Many thanks for any help.