Bug 28244 – mkinitrd hangs kernel > 2.4.2-pre1

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 28244 - mkinitrd hangs kernel > 2.4.2-pre1

Summary:	mkinitrd hangs kernel > 2.4.2-pre1

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	mkinitrd (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	i386 Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Matt Wilson
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-02-18 21:19 EST by Bryan Headley
Modified:	2005-10-31 17:00 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-02-20 20:25:32 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bryan Headley 2001-02-18 21:19:41 EST

From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.1-ac18 i686)


mkinitrd hangs while running mke2fs on loop device. Running mke2fs in
debugger, it's failing in zapbootblock(), in the write(). Running losetup
(with no params) reports the loop device -> relationship, then IT hangs,
most likely in the close() (lomount.c:95)

Am using: losetup-2.10r-2
mount-2.10r-2
mkinitrd-3.0.5-2
kernel 2.4.2-pre{3,4} 2.4.1-ac13 and above.
Have not built util-linux-2.10r that has new mount and new losetup yet.


Reproducible: Always
Steps to Reproduce:
1. Build a kernel. Run mkinitrd to make the image file.
2. Need to be running kernel 2.4.2-pre3 or later
3.
	

Actual Results:  Hangs that processes. Worst: can't do a shutdown
afterwards, unless you're smart enough to unmount all fs's to read-only.
Then, shutdown will hang, but it won't need a fsck...

Expected Results:  Works

[root@cactus /proc]# losetup /dev/loop0
/dev/loop0: [0801]:99103 (/tmp/initrd.img.yR1IS0) offset 0, no encryption

^^losetup loosing it's lunch^^

Comment 1 Matt Wilson 2001-02-19 15:17:59 EST

Only the *stock* kernels have all the necessary loopback patches.  When you
build your own you're on your own (until these get fixed upstream).

If the stock kernel in fisher doesn't work, please reopen.

Comment 2 Bryan Headley 2001-02-20 20:25:29 EST

Interestingly enough, applying Jakub's patch to 2.4.2-pre4 doesn't help it. I'm
not sure why it would anyway, as it deals with changing the FD on the losetup'd
file. How does an lseek to offset 0 followed by a write (to zap the boot sector)
in mke2fs be affected by a patch that adds a 'change-fd ioctl' call?

Anyway,

1) 2.4.0-0.99.11enterprise seems to work with the patch
2) 2.4.2-pre4 does not. And I'm not sure (see above) that the patch was trying
to do anything
   specifically related to this issue. Which means if I'm right you might have
problems with 2.4.2

Comment 3 Matt Wilson 2001-02-21 11:49:30 EST

we won't have a problem with 2.4.2 because we'll test it and fix it if it is
broken.  The only thing that we can support is the kernel as shipped with the
release you're using.

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