Bug 439193 - Assertion failure in journal_next_log_block
Assertion failure in journal_next_log_block
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
i386 Linux
high Severity high
: rc
: ---
Assigned To: Josef Bacik
Martin Jenner
Depends On: 183119
Blocks: KernelPrio5.3
  Show dependency treegraph
Reported: 2008-03-27 10:39 EDT by Josef Bacik
Modified: 2009-01-20 14:55 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 14:55:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch for this bz. (3.60 KB, patch)
2008-05-21 11:29 EDT, Josef Bacik
no flags Details | Diff

  None (edit)
Comment 1 Josef Bacik 2008-05-21 11:29:33 EDT
Created attachment 306266 [details]
patch for this bz.

Here is the patch that will fix this problem.
Comment 4 Don Zickus 2008-07-18 16:07:08 EDT
in kernel-2.6.18-98.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5
Comment 8 Marc Bejarano 2008-12-23 18:14:22 EST
just so it's documented, i've been hitting this assertion regularly in the real world on an 8-core MySQL server.  see SR 1880910.
Comment 9 Josef Bacik 2008-12-24 07:56:34 EST
please test one of the kernels above, the fix is in there.
Comment 11 Marc Bejarano 2009-01-16 16:15:16 EST
hi, josef.  shortly after seeing the problem, we switched to using straight from kernel.org.  it includes the fix that don has in his test kernels.  i installed one of don's test kernels, but i'm not going to reboot unless i have to.

Comment 12 errata-xmlrpc 2009-01-20 14:55:08 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.