Bug 471979 - mkinitrd partitionable (mdp) raid support
mkinitrd partitionable (mdp) raid support
Product: Fedora
Classification: Fedora
Component: mkinitrd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-11-17 19:41 EST by Tomáš Trnka
Modified: 2009-05-06 11:55 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-06 11:55:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch solving the problem (1.39 KB, patch)
2008-11-17 19:41 EST, Tomáš Trnka
no flags Details | Diff

  None (edit)
Description Tomáš Trnka 2008-11-17 19:41:26 EST
Created attachment 323820 [details]
Patch solving the problem

Description of problem:
mkinitrd doesn't support partitionable raid arrays (/dev/md/dXXpYY). If the root device is on such partition, it isn't recognized as RAID at all.

How reproducible:
Simply - create a partitionable raid array and set it as the / device.

Expected results:
The partition should be recognized as a RAID array, the /dev/md/dXX array should be assembled&started on boot

Additional info:
Attached is a patch fixing this problem (against 6.0.68, but I'm using it with v6.0.52 from F9 without any problems).
Additionally, the patch adds support for the structured naming of old-style non-partitionable arrays (i.e. /dev/md/0 instead of /dev/md0).

There's only a minor problem left: nash isn't able to resolve mdp partitions based on UUID/LABEL, so you have to specify the device name directly in fstab.
Comment 1 Jeremy Katz 2009-05-06 11:55:36 EDT
At this point, we're not going to support this in current mkinitrd.  Support for this type of raid is planned with the new initramfs generator planned for Fedora 12 (dracut)

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