Messages in this thread | | | From | Jan-Derk Bakker <> | Subject | EXT2-fs panic on 2.0.30 | Date | Thu, 7 Aug 1997 10:59:52 +0200 (MET DST) |
| |
Hello all,
Just this morning I found this message in my rlogin-window:
Message from syslogd@thorgal at Thu Aug 7 00:03:19 1997 ... thorgal kernel: Kernel panic: EXT2-fs panic (device 08:13): ext2_read_inode: unable to read i-node block - inode=659490, block=2637848
The machine stull runs (is that supposed to happen after a panic ?), and has a lot of zombie processes (top say 311, still increasing).
This machine has experienced odd behavior earlier: Apr 1 00:00:01 thorgal kernel: EXT2-fs warning (device 08:13): ext2_free_blocks : bit already cleared for block 686722 Apr 1 00:00:01 thorgal last message repeated 6 times Apr 1 00:00:01 thorgal kernel: EXT2-fs warning (device 08:13): ext2_free_blocks : bit already cleared for block 686664 Apr 1 00:00:01 thorgal last message repeated 7 times Apr 1 00:00:01 thorgal kernel: EXT2-fs warning (device 08:13): ext2_free_blocks : bit already cleared for block 686693 Apr 1 00:00:01 thorgal last message repeated 2 times Apr 1 00:00:01 thorgal kernel: EXT2-fs warning (device 08:13): ext2_free_blocks : bit already cleared for block 686721 Apr 1 00:03:06 thorgal kernel: EXT2-fs warning (device 08:13): ext2_free_blocks : bit already cleared for block 686664 Apr 1 00:03:06 thorgal last message repeated 7 times Apr 1 00:03:06 thorgal kernel: EXT2-fs warning (device 08:13): ext2_free_blocks : bit already cleared for block 686693 Apr 1 00:03:06 thorgal last message repeated 2 times Apr 1 00:03:06 thorgal kernel: EXT2-fs warning (device 08:13): ext2_free_blocks : bit already cleared for block 686721 Apr 1 00:03:06 thorgal kernel: EXT2-fs warning (device 08:13): ext2_free_inode: bit already cleared for inode 149415
...and later on that day the machine refused to start new processes, and was rebooted. (Yeah, I know, should have reported/fixed it sooner.)
The machine runs a patchless 2.0.30 for almost 37 days now. It is a PPro that runs as a server (hence no X weirdness). The SCSI card is a BusLogic BT-948: Bus 0, device 9, function 0: SCSI storage controller: BusLogic MultiMaster (rev 8). Fast devsel. IRQ 9. Master Capable. Latency=32. Min Gnt=8.Max Lat=8. I/O at 0xe000. Non-prefetchable 32 bit memory at 0xfbfcf000.
...and the disks are Fujitsu: Vendor: FUJITSU Model: M2934S-512 Rev: 0122 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 Vendor: FUJITSU Model: M2934S-512 Rev: 0122 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
As it is the holiday season, things are relatively quiet, and if anyone has patches/recommendations I should be able to test them.
Sincerely,
Jan-Derk Bakker.
| |