Re: 2.6.11.11 Assertion failure in journal_commit_transaction()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  Hello,

> On a busy server (dual Xeon with 4GB ram) running plain 2.6.11.11 form
> kernel.org (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 2.6.11.11
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
								Honza

-- 
Jan Kara <[email protected]>
SuSE CR Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux