I've seen this behavior before (I never reported it either mostly
because a AHA 1740 driver bug was the alleged cause...this was a while
back). The solution in my case seem to be a massive backup and repeated
low level formats on the culprit drive or just returning the drive for
replacement. The system did not have a Bus Logic controller. However I
think the culprit drive was a Fujitsu! (could be wrong)
Anybody out there have this problem and have Fujitsu in common?
Interesting test:
Reboot and try:
dd if=/dev/<culprit drive> of=/dev/null
and see if near the end of the drive it starts spewing. Betcha it does.
You will begin to lose data with this kind of problem if its anything like the
problem I had. Backups would be prudent.
Glenn Bily
>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: