[lkml]   [2005]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Assertion failure in journal_commit_transaction()

    > On a busy server (dual Xeon with 4GB ram) running plain form
    > (distribution is Fedora Core 2) I got the following error:
    > Jun 4 11:40:55 apollo kernel: Assertion failure in
    > journal_commit_transaction() at fs/jbd/commit.c:768:
    > "jh->b_next_transaction == ((void *)0)"
    > Jun 4 11:40:55 apollo kernel: ------------[ cut here ]------------
    > Jun 4 11:40:55 apollo kernel: kernel BUG at fs/jbd/commit.c:768!
    > Jun 4 11:40:55 apollo kernel: invalid operand: 0000 [#1]
    > Jun 4 11:45:07 apollo syslogd 1.4.1: restart.
    > The system bootet automatically, from the ipmi motherboard logs I can see
    > that the hardware watchdog has reset the system at 11:42:55.
    > It's using an ext3 on top of a software raid10 (three raid1 combined with
    > raid0 over 6 SCSI disks). None of the software raids needed to rebuild after
    > the crash.
    > Any idea why the kernel stopped? The system has been running stable for a
    > year now.
    The kernel stopped because it detected a disk buffer in an unexpected
    state. 2.6.12-rc5 kernel should contain some more fixes than
    for similar problems so you can try that kernel. If you are able to see
    the same problem with 2.6.12-rc5 then let us know please.

    Thanks for report

    Jan Kara <>
    SuSE CR Labs
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-06-06 15:46    [W:0.022 / U:33.172 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site