Linux 2.0.27 kernel crashing

Rob Allen (roba@ntscom.com)
Tue, 31 Dec 1996 15:47:51 -0600

I have been experiencing problems with my usenet news server lately and I
think I finally found the cause, and hopefully someone here will recognize
a solution. What is happening is the server crashes, OS and all, between
12-24 hours of uptime while receiving a full usenet news feed. I have
pasted below the last part of the kernel messages that syslogd reports. It
looks as if every minute or so I get the EXT2-fs error on a particular
inode, and finally leads up to the kernel crashing. I find that the kernel
crashes after about 4-5 hours after the errors start.

Here's the system:
Pentium Pro 200Mhz
256Megs Ram
Linux 2.0.27 (RedHat 4.0 installed)
Adaptec 3940W SCSI controller
2 Seagate 4.1Gig Baraccuta (one on each channel of the contoller)

I'm hoping someone here can give me a direction to go here... I have
thought that maybe the drive is going bad? I have 4 more 4Gig drives that I
would like to put online, but I need to have the problem resolved first. If
you need more info PLEASE let me know.

Thanks for your help,
-Rob
roba@ntscom.com

----------------- part of *.info from syslogd --------------------------
Dec 28 17:56:53 news kernel: EXT2-fs error (device 08:11): ext2_find_entry:
bad entry in directory #79873: rec_len % != 0 - offset=0,
inode=1226980165, rec_len=16733, name_len=23123
Dec 28 17:56:53 news kernel: EXT2-fs error (device 08:11): ext2_find_entry:
bad entry in directory #79873: rec_len % != 0 - offset=0,
inode=1226980165, rec_len=16733, name_len=23123
Dec 28 17:56:53 news kernel: EXT2-fs error (device 08:11): ext2_add_entry:
bad entry in directory #79873: rec_len % != 0 - offset=0,
inode=1226980165, rec_len=16733, name_len=23123
Dec 28 17:56:53 news kernel: EXT2-fs error (device 08:11): ext2_find_entry:
bad entry in directory #79873: rec_len % != 0 - offset=0,
inode=1226980165, rec_len=16733, name_len=23123
Dec 28 17:56:53 news kernel: EXT2-fs error (device 08:11): ext2_add_entry:
bad entry in directory #79873: rec_len % != 0 - offset=0,
inode=1226980165, rec_len=16733, name_len=23123
Dec 28 17:57:54 news kernel: EXT2-fs error (device 08:11): ext2_find_entry:
bad entry in directory #79873: rec_len % != 0 - offset=0,
inode=1226980165, rec_len=16733, name_len=23123
Dec 28 17:58:38 news kernel: EXT2-fs error (device 08:11): ext2_find_entry:
bad entry in directory #434178: rec_len % != 0 - offset=0,
inode=1752457552, rec_len=8250, name_len=25966
Dec 28 17:59:06 news kernel: EXT2-fs error (device 08:11): ext2_find_entry:
bad entry in directory #434182: rec_len % != 0 - offset=0,
inode=1752457552, rec_len=8250, name_len=25966
Dec 28 17:59:06 news kernel: EXT2-fs error (device 08:11): ext2_add_entry:
bad entry in directory #434182: rec_len % != 0 - offset=0,
inode=1752457552, rec_len=8250, name_len=25966
Dec 28 17:59:06 news kernel: EXT2-fs error (device 08:11): ext2_add_entry:
bad entry in directory #434182: rec_len % != 0 - offset=0,
inode=1752457552, rec_len=8250, name_len=25966
Dec 28 17:59:55 news kernel: Unable to handle kernel paging request at
virtual address f621223c
Dec 28 17:59:55 news kernel: current->tss.cr3 = 0f17a000, (r3 = 0f17a000
Dec 28 17:59:55 news kernel: *pde = 00000000
Dec 28 17:59:55 news kernel: Oops: 0000
Dec 28 17:59:55 news kernel: CPU: 0
Dec 28 17:59:55 news kernel: EIP: 0010:[get_hash_table+48/180]
Dec 28 17:59:55 news kernel: EFLAGS: 00010216
Dec 28 17:59:55 news kernel: eax: 3621223c ebx: 00130811 ecx: 0496e0b4
edx: 00004556
Dec 28 17:59:55 news kernel: esi: 00134439 edi: 00000811 ebp: 00134c28
esp: 0f17bd78
Dec 28 17:59:55 news kernel: ds: 0018 es: 0018 fs: 002b gs: 002b
ss: 0018
Dec 28 17:59:55 news kernel: Process overchan (pid: 283, process nr: 11,
stackpage=0f17b000)
Dec 28 17:59:55 news kernel: Stack: 00134c28 00000001 04960811 00000400
0f17be5c 00123125 00000811 00134c28
Dec 28 17:59:55 news kernel: 00000400 00134c28 00000010 0496e000
00000000 00000400 0f17be5c 00157e3b
Dec 28 17:59:55 news kernel: 00000811 00134c28 00000400 00000008
00000010 0f17be5c 0496e000 00000002
Dec 28 17:59:55 news kernel: Call Trace: [newseg+416/424] [getblk+49/1112]
[newseg+416/424] [newseg+416/424] [inode_getblk+67/400] [newseg+416/424]
[ext2_getblk+225/528]
Dec 28 17:59:55 news kernel: [ext2_file_write+387/1108]
[generic_file_read+0/1472] [ext2_file_write+0/1108] [getblk+49/1112]
[sys_semctl+1060/2204] [sys_semctl+1060/2204] [bread+22/120] [__brelse+34/68]
Dec 28 17:59:55 news kernel: [ext2_read_inode+605/784]
[do_readv_writev+534/596] [ext2_file_write+0/1108] [sys_chdir+28/152]
[sys_writev+95/120] [system_call+85/128]
Dec 28 17:59:55 news kernel: Code: 39 28 75 28 66 39 58 04 75 22 8b 4c 24
20 39 48 20 74 22 57

------------------------------- syslogd --------------------------
The system is now dead...

.
+--------------------------------------------------------------------+
| _/ _/ _/_/_/_/_/ _/_/_/_/ Rob Allen |
| _/_/ _/ _/ _/ Internet Administrator |
| _/ _/ _/ _/ _/_/_/ NTS Communications, Inc. |
| _/ _/_/ _/ _/ (806) 762-4565 ext. 4110 |
| _/ _/ _/ _/_/_/_/ E-Mail: roba@ntscom.com |
+--------------------------------------------------------------------+