Bug 104076

Summary:	bad initrd created for 2.4 kernel installed when running 2.6
Product:	[Retired] Red Hat Linux Beta	Reporter:	Michael Young <m.a.young>
Component:	mkinitrd	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED WORKSFORME	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	beta1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-10-01 20:32:10 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 Michael Young 2003-09-09 17:12:19 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.2.1) Gecko/20030711

Description of problem:
I have seen this a couple of times, after installing a new 2.4 severn kernel
while one of arjan's 2.6 kernel is running. When you try to boot the 2.4 kernel,
you get errors suggesting that that the kernel is trying to read beyond the end
of the initrd. Re-running mkinitrd by hand creates a good initrd, as does
fscking the original initrd and recompressing. The contents when mounted of
these initrds are the same, (diff -r complains at the special files in dev, but
only the timestamps appear to be different), though the original one complains
that recovery might be needed when mounting.

Comment 1 Jeremy Katz 2003-09-29 23:26:00 UTC

Does 'tune2fs -l' on the filesystems show different flags?

Comment 2 Jeremy Katz 2003-10-01 20:32:10 UTC

Could have just been a flaky 2.6 kernel with loop devs or something like that. I
haven't seen it in my switching back and forth between kernels, but I've missed
a few, too.