Bug 80424 - mkinitrd should not need /etc/raidtab to determine if raid modules are needed
mkinitrd should not need /etc/raidtab to determine if raid modules are needed
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Erik Troan
David Lawrence
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-25 22:29 EST by Jordan Russell
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-14 17:18:41 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)
Proposed fix for the problem (1.03 KB, patch)
2002-12-25 22:35 EST, Jordan Russell
no flags Details | Diff

  None (edit)
Description Jordan Russell 2002-12-25 22:29:58 EST
***patch included***

Description of problem:
mkinitrd has an unnecessary requirement that /etc/raidtab exist and be up-to-
date in order for it to include necessary raid modules.

Many including myself no longer create or use /etc/raidtab files with the 
advent of the "mdadm" utility.

Version-Release number of selected component (if applicable):
mkinitrd-3.4.28-1
Comment 1 Jordan Russell 2002-12-25 22:35:24 EST
Created attachment 88912 [details]
Proposed fix for the problem

This patch makes mkinitrd parse /proc/mdstat in addition to /etc/raidtab to
find out which raid modules are being used and thus needed.

This also makes the raid detection more like the other types of detection in
that it checks what's actually being used in the currently running kernel, and
not merely what a file claims is needed.
Comment 2 Erik Troan 2003-01-14 17:18:41 EST
mkinitrd and grubby now use /proc/mdstat instead of /etc/raidtab -- good call

you'll see this in the version > 3.4.43

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