Re: 2.4.24 ext3 oops

[Gabor Burjan]

Hi,

Exactly the same error on another filesystem (/usr).  Now I can attach
the output of fsck.

Gabor

Attachment: sz-usr-ext3-fs-errors.log.gz
Description: Binary data

Assertion failure in journal_forget() at transaction.c:1255: "!jh->b_committed_data"
kernel BUG at transaction.c:1255!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c01735c6>]    Tainted: GF
EFLAGS: 00010286
eax: 00000058   ebx: eab63300   ecx: e1b2c000   edx: d34c53d4
esi: dd118340   edi: efd431f4   ebp: e1b2dde8   esp: e1b2ddc0
ds: 0018   es: 0018   ss: 0018
Process rm (pid: 31453, stackpage=e1b2d000)
Stack: c02a0ba0 c029db3e c029d9b6 000004e7 c029db4d efd43180 ef7e7dc0 eab63300 
efd43180 eab63300 e1b2de10 c017729d d919dfe0 eab63300 00000000 00000001 
c6e1f080 eab63300 c6e1f080 d919dfe0 e1b2de44 c0168f95 d919dfe0 00010000 
Call Trace:    [<c017729d>] [<c0168f95>] [<c013da90>] [<c016b5e6>] [<c01690fc>]
[<c016bb53>] [<c0172250>] [<c01690fc>] [<c016929b>] [<c016eabd>] [<c0169190>]
[<c01511ce>] [<c0147ad0>] [<c0147ce2>] [<c010930f>]

Code: 0f 0b e7 04 b6 d9 29 c0 e9 61 ff ff ff c7 44 24 10 63 db 29 
ksymoops 2.4.9 on i686 2.4.24.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.24/ (default)
     -m /boot/System.map-2.4.24 (specified)

kernel BUG at transaction.c:1255!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c01735c6>]    Tainted: GF
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 00000058   ebx: eab63300   ecx: e1b2c000   edx: d34c53d4
esi: dd118340   edi: efd431f4   ebp: e1b2dde8   esp: e1b2ddc0
ds: 0018   es: 0018   ss: 0018
Process rm (pid: 31453, stackpage=e1b2d000)
Stack: c02a0ba0 c029db3e c029d9b6 000004e7 c029db4d efd43180 ef7e7dc0 eab63300 
efd43180 eab63300 e1b2de10 c017729d d919dfe0 eab63300 00000000 00000001 
c6e1f080 eab63300 c6e1f080 d919dfe0 e1b2de44 c0168f95 d919dfe0 00010000 
Call Trace:    [<c017729d>] [<c0168f95>] [<c013da90>] [<c016b5e6>] [<c01690fc>]
[<c016bb53>] [<c0172250>] [<c01690fc>] [<c016929b>] [<c016eabd>] [<c0169190>]
[<c01511ce>] [<c0147ad0>] [<c0147ce2>] [<c010930f>]
Code: 0f 0b e7 04 b6 d9 29 c0 e9 61 ff ff ff c7 44 24 10 63 db 29 


>>EIP; c01735c6 <journal_forget+1a6/1f0>   <=====

>>ebx; eab63300 <_end+2a803f28/3050fc88>
>>ecx; e1b2c000 <_end+217ccc28/3050fc88>
>>edx; d34c53d4 <_end+13165ffc/3050fc88>
>>esi; dd118340 <_end+1cdb8f68/3050fc88>
>>edi; efd431f4 <_end+2f9e3e1c/3050fc88>
>>ebp; e1b2dde8 <_end+217cea10/3050fc88>
>>esp; e1b2ddc0 <_end+217ce9e8/3050fc88>

Trace; c017729d <journal_revoke+bd/170>
Trace; c0168f95 <ext3_forget+85/120>
Trace; c013da90 <bread+20/90>
Trace; c016b5e6 <ext3_free_branches+e6/2a0>
Trace; c01690fc <start_transaction+8c/90>
Trace; c016bb53 <ext3_truncate+3b3/450>
Trace; c0172250 <journal_start+a0/c0>
Trace; c01690fc <start_transaction+8c/90>
Trace; c016929b <ext3_delete_inode+10b/160>
Trace; c016eabd <ext3_unlink+ed/1d0>
Trace; c0169190 <ext3_delete_inode+0/160>
Trace; c01511ce <iput+fe/220>
Trace; c0147ad0 <vfs_unlink+d0/1e0>
Trace; c0147ce2 <sys_unlink+102/110>
Trace; c010930f <system_call+33/38>

Code;  c01735c6 <journal_forget+1a6/1f0>
00000000 <_EIP>:
Code;  c01735c6 <journal_forget+1a6/1f0>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c01735c8 <journal_forget+1a8/1f0>
   2:   e7 04                     out    %eax,$0x4
Code;  c01735ca <journal_forget+1aa/1f0>
   4:   b6 d9                     mov    $0xd9,%dh
Code;  c01735cc <journal_forget+1ac/1f0>
   6:   29 c0                     sub    %eax,%eax
Code;  c01735ce <journal_forget+1ae/1f0>
   8:   e9 61 ff ff ff            jmp    ffffff6e <_EIP+0xffffff6e>
Code;  c01735d3 <journal_forget+1b3/1f0>
   d:   c7 44 24 10 63 db 29      movl   $0x29db63,0x10(%esp,1)
Code;  c01735da <journal_forget+1ba/1f0>
  14:   00 

# fsck.ext3 /dev/md1
e2fsck 1.34 (25-Jul-2003)
/dev/md1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 72903 has illegal block(s).  Clear<y>? yes

Illegal block #8 (1067873398) in inode 72903.  CLEARED.
Illegal block #9 (1067873441) in inode 72903.  CLEARED.
Illegal block #10 (1067873398) in inode 72903.  CLEARED.
Illegal block #12 (4294967295) in inode 72903.  CLEARED.
Illegal block #13 (4294967295) in inode 72903.  CLEARED.
Illegal block #14 (4294967295) in inode 72903.  CLEARED.
Illegal block #15 (4294967295) in inode 72903.  CLEARED.
Illegal block #16 (4294967295) in inode 72903.  CLEARED.
Illegal block #17 (4294967295) in inode 72903.  CLEARED.
Illegal block #18 (4294967295) in inode 72903.  CLEARED.
Illegal block #19 (4294967295) in inode 72903.  CLEARED.
Too many illegal blocks in inode 72903.
Clear inode<y>? yes

Restarting e2fsck from the beginning...
/dev/md1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'mace.c' in /src/linux-2.4.22/drivers/net (73832) has deleted/unused inode 72903.  Clear<y>? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  +(65536--65791) -(376648--376655)
Fix<y>? yes

Free blocks count wrong for group #11 (15656, counted=15664).
Fix<y>? yes

Free blocks count wrong (74444, counted=74452).
Fix<y>? yes

Inode bitmap differences:  -72903
Fix<y>? yes

Free inodes count wrong for group #4 (7123, counted=7124).
Fix<y>? yes

Free inodes count wrong (103749, counted=103750).
Fix<y>? yes


/dev/md1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/md1: 140570/244320 files (3.9% non-contiguous), 413724/488176 blocks