Bug 55616

Summary:	ext3 assertion failure with 2.4.9-7.4smp
Product:	[Retired] Red Hat Linux	Reporter:	Jeremy Katz <katzj>
Component:	kernel	Assignee:	Stephen Tweedie <sct>
Status:	CLOSED WORKSFORME	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	ia64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-11-15 10:33:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeremy Katz 2001-11-02 22:04:36 UTC

Message on console is

Assertion failure in unmap_underlying_metadata() at buffer.c:1540:
"!buffer_jlist_eq(old_bh,3)"

Nothing at all special was being done on the ia64, mainly just sitting
there turned on.  Also, am now unable to log in on the console and the
already logged in shell is reporting that it can't fork() anymore...

Unfortunately, nothing useful or interesting in syslog

Comment 1 Stephen Tweedie 2001-11-13 18:42:30 UTC

The console message should include a backtrace.  Did you capture that?

Comment 2 Jeremy Katz 2001-11-13 19:50:04 UTC

Unfortunately, there wasn't one

Comment 3 Stephen Tweedie 2001-11-14 18:02:08 UTC

Did you have a serial console set up?

Comment 4 Jeremy Katz 2001-11-14 18:10:33 UTC

No, the machine is generally reinstalled on a multiple times a day basis for
anaconda testing...  it just happened to actually sit turned on for a few days
for a change and I happened to notice it.

Comment 5 Stephen Tweedie 2001-11-15 10:32:59 UTC

Is this box normally reliable?  We do Cerberus testing on ia64 regularly and
have never seen anything like this, and the last time I got a bad b_jlist
report, it turned out to be bad ram.

Comment 6 Stephen Tweedie 2002-01-17 18:33:51 UTC

Please reopen this bug if you can reproduce it.