Bug 204742 - mkinitrd heuristics for setting 'needusb' break for LVM
Summary: mkinitrd heuristics for setting 'needusb' break for LVM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: mkinitrd
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Brian Lane
QA Contact: Kevin Baker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-31 12:15 UTC by lars
Modified: 2014-12-01 23:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-27 17:59:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch for simpler building of usb-enabled initrd images. (976 bytes, patch)
2006-08-31 12:15 UTC, lars
no flags Details | Diff

Description lars 2006-08-31 12:15:45 UTC
With root on an LVM VG that includes a USB attached disk, it's not possible to have mkinitrd 
automatically generate a working initrd image (it is possible if you manually specify the appropriate 
modules with --preload).

The problem is largely the small block of code that attempts to figure out whether or not the USB 
modules are necessary by explicitly checking to see if /boot or /root is on a USB attached device.  This 
test is far too clever by half, and in an LVM environment will never succeed.

Rather than trying to "fix" the test so that it works correctly, I think the best solution is to simply 
remove this test and have the "--with-usb" command line option simply cause mkinitrd to include the 
USB modules.  Trying to outsmart the sysadmin with clever shell scripts is generally a recipe doomed to 
failure.

I've attached a patch to mkinitrd that makes this change.

Comment 1 lars 2006-08-31 12:15:45 UTC
Created attachment 135277 [details]
Patch for simpler building of usb-enabled initrd images.


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