Bug 171855
| Summary: | can't create degraded raid 4 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <aoliva> |
| Component: | mdadm | Assignee: | Doug Ledford <dledford> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-10-27 06:18:30 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: | |||
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8b5) Gecko/20051008 Fedora/1.5-0.5.0.beta2 Firefox/1.4.1 Description of problem: Attempting to create a degraded raid 4 array produces the following output: # mdadm -C /dev/md31 -l 4 -n 3 /dev/loop0 /dev/loop1 missing mdadm: RUN_ARRAY failed: Input/output error (It's not about the use of loop devices; I've actually run into this with actual hard disk partitions.) Sure enough, the last syscall that mdadm issues to the kernel fails with -EIO, but I can't tell whether that's because the kernel is in error, or if mdadm is passing incorrect parameters to the kernel. Doing the very same operation with -l 5 works, FWIW. On the Fedora development tree, the raid components have already got their raid superblocks written out (or so it seems to me), so a subsequent assemble brings up the degraded raid successfully. However, on a fully-updated FC4 box, I have no such luck: the superblocks there don't match each other, so nothing happens. Version-Release number of selected component (if applicable): mdadm-1.11.0-4.fc4 kernel-2.6.13-1.1622_FC5 How reproducible: Always Steps to Reproduce: 1.mdadm -C -l 4 -n 3 /dev/loop{0,1} missing Actual Results: -EIO in the last ioctl, the one that, replacing -l4 with -l5, immediately precedes the write() stating that the array was brought up successfully. Expected Results: It would be nice if this worked. Additional info: