Bug 128169

Summary: mkinitrd *hangs* when kernel doesn't have block loopback support
Product: [Fedora] Fedora Reporter: Bob T. <rdtennent>
Component: mkinitrdAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-02 22:32:52 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 Bob T. 2004-07-19 15:53:56 UTC 
Description of problem:  The summary says it all.  I know what the man
page says; it's just that hanging isn't an acceptable response. The
script should test for block loopback support and produce a useful
error message if it's not there.  Mkinitrd is a hidden step for
installing a kernel and if one has removed block loopback support in
building a custom kernel, it may not be until months later that one
finds it impossible to install a new kernel after hours of compilation
with no indication of what the problem is.  And it wouldn't hurt to
put a warning comment in the kernel configuration script so this
apparently useless feature won't be removed so easily.
Comment 1 Jeremy Katz 2004-08-02 22:32:52 UTC 
This won't be a problem with mkinitrd 4.x and 2.6 kernels.