Bug 77386 - Assertion failure in journal_write_metadata_buffer() at journal.c:408: "buffer_jdirty(jh2bh(jh_in))"
Assertion failure in journal_write_metadata_buffer() at journal.c:408: "buffe...
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.3
i686 Linux
high Severity high
: ---
: ---
Assigned To: Stephen Tweedie
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-06 00:47 EST by Lim Chuan Jer
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-28 18:51:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
LogFile Error code (1.19 KB, text/plain)
2002-11-06 00:58 EST, Lim Chuan Jer
no flags Details
Error message as found in the system logfile after rebooting. (1.99 KB, text/plain)
2003-01-23 17:05 EST, Robert Treat
no flags Details

  None (edit)
Description Lim Chuan Jer 2002-11-06 00:47:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
My server running SMP 2.14.8.5 kernel (RedHAt 7.3).
Equipeded with 2 P3 933MHz and 1 GB RAM

Suddenly hanged up on me. Still pingable but all services dead. Upon rebooting, 
look through the log file and found the kernel error code. I've attached as 
attachment.

Any idea why is that so?


Version-Release number of selected component (if applicable):


How reproducible:
Didn't try


Additional info:

I search thru the repository and can only find a similar entry titled 
Assertion failure in journal_write_metadata_buffer() at 
journal.c:406: "buffer_jdirty(jh2bh(jh_in))"

But what i got at my system is c:408 instead of c:406. Not too sure whats the 
difference.
Comment 1 Lim Chuan Jer 2002-11-06 00:58:09 EST
Created attachment 83806 [details]
LogFile Error code
Comment 2 Stephen Tweedie 2002-11-06 09:44:45 EST
Have you seen any similar problems before?  Was there _anything_ else in the
logs related to possible ext3 or IO problems?
Comment 3 Lim Chuan Jer 2002-11-06 10:36:43 EST
This is the 2nd time I encounter it on the same machine in 4 months time. Not 
very frequent, but is interested to know whats the cause of it
Comment 4 Robert Treat 2003-01-23 17:05:31 EST
Created attachment 89554 [details]
Error message as found in the system logfile after rebooting.
Comment 5 Robert Treat 2003-01-24 16:41:07 EST
I posted the logfile yesterday, here is the explination: We recieved this error
on our server running Red Hat 7.3 and 2.4.18-5smp. The server is a dedicated
postgresql database server. I noticed in the last message for bug # 64107 that
the error was recieved on heavy IO load, and I think this might have been a
similar problem for us.  We had turned on query logging on our database which
was producing data at a rate of about 2.6GB in around 6 hours. Once the error
occured, we had no access to the server and had to power off/on. 
Comment 6 Stephen Tweedie 2003-01-28 18:51:27 EST
2.4.18-3 had a problem that triggered this quite frequently, and that was fixed
in 2.4.18-5.  However, I found another rare case that could sometimes still
cause it even in that kernel, and that should be fixed in all subsequent errata
later than 2.4.18-5.  Please reopen this report if you still have the problem on
a current kernel.

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