Bug 252123
Summary: | mdadm should only accepts hard disk partitions of type 0xFD, "Linux raid" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | zic <zic-rhn> |
Component: | mdadm | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-14 08:09:32 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
zic
2007-08-14 01:06:48 UTC
That fdisk only prints "Linux Raid" as the partition type for 0xfd is misleading in that the full name is "Linux Raid Autodetect". Linux md raid devices were never intended to be constrained to only partition type 0xfd. With the advent of improved stacked raid array support in the kernel and mdadm, it's in fact impossible to constrain mdadm to a single partition type and support the many ways in which it is used. Instead, mdadm examines the beginning of any partition to see if it already has A) an mdadm device on it or B) one of the common linux filesystems on it. If it does, it asks the operator if they really want to use the device in the array before continuing. It is probably arguable that it should check for lvm superblocks as well, but that's an upstream feature enhancement issue and is likely beyond the scope of what I would want to carry as an additional patch to mdadm. Please send an email about your concerns to the linux-raid.org mailing list. The author of mdadm reads that list regularly and would likely implement the needed fix, at which point we'll pick it up in an update. |