Assertion failure in do_get_write_access()

Yuri van Oers yvanoers at
Sun Jun 26 13:30:42 UTC 2005


I just had my server cry this out to the console:

Assertion failure in do_get_write_access() at transaction.c:658:
"jh->b_transaction == journal->j_committing_transaction"
kernel BUG at transaction.c:658!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c015e1f6>]    Not tainted
EFLAGS: 00010286
eax: 0000007d   ebx: c2ff4200   ecx: c243e000   edx: c068af00
esi: c0d6d900   edi: c2ff4200   ebp: c03f4190   esp: c243fd44
ds: 0018   es: 0018   ss: 0018
Process gzip (pid: 28630, stackpage=c243f000)
Stack: c0273660 c027385b c0273640 00000292 c0273920 c2ff4200 c18dd660 c03f4190
       c2ff4294 00000001 c0155dd6 00000000 00000000 00000000 c2f0f740 00000000
       c243fdc4 c243fdc4 c2ff4200 c015e4c8 c18dd660 c03f4190 00000000 00000006
Call Trace:    [<c0155dd6>] [<c015e4c8>] [<c0156337>] [<c015668d>] [<c0156788>]
  [<c01319d2>] [<c013226e>] [<c015672c>] [<c0156bc5>] [<c015672c>] [<c0125685>]
  [<c0125ae3>] [<c0117856>] [<c0154906>] [<c012f766>] [<c0106b63>]

Code: 0f 0b 92 02 40 36 27 c0 83 c4 14 8b 45 08 83 f8 06 0f 85 85

The version of Linux is 2.4.28. It took a hardware reset to get
/dev/sda2 (the partition with the fs I suspect was aching) back online. At
the time of the error I was tarring jpegs to that partition.

I could not find any references to this sort of bug being encountered or
fixed after 2.4.28, so I felt obliged to report it.

Is it a known bug? If so, has it been fixed? If not, can it be fixed & do
you need my help or any other info?


More information about the Ext3-users mailing list