It suddenly showed filesystem corruption last night (this was during a
backup run unfortunately...) and several funny things afterwards. I
post the relevant part of the log file here. Any help????
-------------snip--------------------------------------------
May 19 01:15:04 britten kernel: EXT2-fs error (device 08:12): ext2_readdir: bad entry in directory #258095: rec_len % 4 != 0 - offset=0, inode=1969974881, rec_len=26478, name_len=28261
May 19 01:15:26 britten kernel: EXT2-fs warning (device 08:12): ext2_free_inode: bit already cleared for inode 895080
May 19 01:15:26 britten kernel: EXT2-fs warning (device 08:12): ext2_free_inode: bit already cleared for inode 895066
May 19 01:15:26 britten kernel: EXT2-fs warning (device 08:12): ext2_free_inode: bit already cleared for inode 895067
<-- many of these above follow -->
May 19 01:15:47 britten kernel: EXT2-fs error (device 08:12): ext2_readdir: bad entry in director
y #258095: rec_len % 4 != 0 - offset=0, inode=1969974881, rec_len=26478, name_len=28261
May 19 01:45:43 britten kernel: EXT2-fs error (device 08:02): ext2_find_entry: bad entry in direc
tory #55533: rec_len is too small for name_len - offset=0, inode=861676079, rec_len=12592, name_l
en=26927
May 19 01:45:53 britten kernel: EXT2-fs error (device 08:02): ext2_find_entry: bad entry in direc
tory #273449: rec_len % 4 != 0 - offset=0, inode=1852387121, rec_len=29797, name_len=8751
May 19 01:45:53 britten last message repeated 17 times
May 19 01:45:58 britten kernel: EXT2-fs error (device 08:02): ext2_find_entry: bad entry in direc
tory #55533: rec_len is too small for name_len - offset=0, inode=861676079, rec_len=12592, name_l
en=26927
May 19 02:05:16 britten kernel: EXT2-fs warning (device 08:12): ext2_free_inode: bit already clea
red for inode 895066
<-- again many of these warnings above follow -->
May 19 02:06:24 britten kernel: EXT2-fs warning (device 08:12): ext2_free_inode: bit already clea
red for inode 258089
May 19 02:06:52 britten kernel: EXT2-fs error (device 08:12): ext2_find_entry: bad entry in direc
tory #874519: directory entry across blocks - offset=0, inode=3041726974, rec_len=60164, name_len
=16514
May 19 02:06:52 britten last message repeated 3 times
May 19 02:07:13 britten sendbackup[11034]: error [/usr/local/bin/tar returned 2]
May 19 02:16:08 britten sendbackup[11008]: error [/usr/local/bin/tar returned 2]
May 19 02:31:19 britten kernel: general protection: 0000
May 19 02:31:19 britten kernel: CPU: 0
May 19 02:31:19 britten kernel: EIP: 0010:[get_hash_table+52/172]
May 19 02:31:19 britten kernel: EFLAGS: 00010202
May 19 02:31:19 britten kernel: eax: 7814940b ebx: 000c0803 ecx: 00000803 edx: 00000814
May 19 02:31:19 britten kernel: esi: 00000803 edi: 000c1017 ebp: 00000400 esp: 043c8ddc
May 19 02:31:19 britten kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
May 19 02:31:19 britten kernel: Process dumper (pid: 10936, process nr: 75, stackpage=043c8000)
May 19 02:31:19 britten kernel: Stack: 000c1017 043c0803 00000400 000c1017 064b7c0c 00000814 0012
55be 00000803
May 19 02:31:19 britten kernel: 000c1017 00000400 000c1017 043c8ef4 001ded84 000c1017 0000
0001 001555b8
May 19 02:31:19 britten kernel: 00000803 000c1017 00000400 00000000 000c1017 00000001 0549
c000 00000400
May 19 02:31:19 britten kernel: Call Trace: [getblk+54/956] [ext2_alloc_block+128/412] [block_get
blk+348/612] [ext2_getblk+385/556] [ext2_file_write+389/1116] [inet_recvmsg+114/136] [sock_read+1
71/192]
May 19 02:31:19 britten kernel: [sys_write+331/388] [system_call+85/124]
May 19 02:31:19 britten kernel: Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 77 f9 ff
and many more of these general protection faults follow, over the
whole night until this morning when I finally (hard-) booted the
machine.
The last kernels have been very stable besides the ppp thing. At least
I haven't seen these gp's since around 2.0.32 or 33 I think.
jtl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu