Bug 214053
| Summary: | Unable to create RAID arrays on FC6 beyond /dev/md0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | J.F.Gratton <grajea01> |
| Component: | mdadm | Assignee: | Doug Ledford <dledford> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6 | CC: | nerijus, pb |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-11-05 15:43:23 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
J.F.Gratton
2006-11-05 07:05:48 UTC
This isn't a bug in mdadm. The devices simply don't exist. They must be created first. You can manually create them, or you can pass the --auto=yes flag to mdadm when creating the arrays and it will make the device nodes for you. Why is FC lacking these nodes? For example, they are pre-created in openSUSE, so users don't run into spurious messages like these. *** Bug 216438 has been marked as a duplicate of this bug. *** udev has: KERNEL=="dm-[0-9]*", ACTION=="add", OPTIONS+="ignore_device" because of bug #204157 From Alasdair Kergon (agk): udev needs to completely ignore the 'add' event, and instead act on the 'change' event. Until the change event arrives under no circumstances should udev attempt to open the dm device or query any dm device properties. In future lvm2 and other applications will then wait until udev has completed processing the 'change' event before proceeding. udev will then be able to assume full responsibility for /dev/mapper - the 'change' event will cause the nodes to be added to /dev. There is no way to do this correctly in response to the existing 'add' event, because the dm properties udev needs to query are not yet defined in-kernel at this point. The 'change' event is the new signal that the properties are now fully defined. sry, ignore my last comment... confused md* vs dm* Why is this bug closed with "NOTABUG"? It is still present and should be solved imho. It's close NOTABUG because there is no bug. The change from a normal, fully populated /dev directory to a udev controlled directory was done to clean up all the useless entries. Pre-populating the directory would be counterproductive towards that original goal. This means that for some activities, specifically ones involving virtual devices that the kernel can't automatically probe, a slightly different method of system administration is now needed. The sysadmin of these systems simply needs to pass the --auto=yes option to mdadm on the same command they use to create the device. Thank you for clarification and the hint with the option "--auto=yes", I was not aware of this. |