Bug 43908
| Summary: | md1 and md10 can't co-exist | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Alexandre Oliva <aoliva> | ||||||
| Component: | raidtools | Assignee: | Arjan van de Ven <arjanv> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 7.1 | CC: | giulioo, nfaerber | ||||||
| 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: | 2003-09-02 21:47:37 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Alexandre Oliva
2001-06-07 21:33:56 UTC
I have the same problem on a rh6.x system with rh6x raidtools-0.90-13. Temporary workaround is to comment out from /etc/raidtab the device that confuses raidtools. This bug is very similar to bug #10111, which was about parsing of /etc/mtab. For RedHat: if you update the rpm for rh71, will it be compatible, unofficially, for rh6x too (ie: can we rebuild src.rpm and use it)? I see in the changelog "updated to support multipath in 2.4.2 kernel" is this something that may cause problems on rh6x? This is because mkraid/raidstop pass "md1" to strstr. Call it with "md1 " for an easy fix. Given that the release in rawhide is raidtools-0.90-23, can you confirm that the behaviour still exists with that version? This bug exists in the most recent rawhide raidtools-1.00.2-3.3. That means 7.2
through 8.0 is affected including Advanced Server.
To reproduce, just create a raidtab with md10 and md1 defined then:
mkraid /dev/md10
mkraid /dev/md1
You will get an error telling you to run 'raidstop' on /dev/md1. A simple patch
follows:
--- raid_io.c.old Wed Aug 28 15:55:15 2002
+++ raid_io.c Wed Aug 28 15:59:20 2002
@@ -523,6 +523,7 @@
if ((ch = strstr(p->md_name, "/md")) == NULL)
return 0;
strcpy(buffer, ch+1);
+ strcpy(buffer, strcat(buffer, " "));
if ((fp = fopen("/proc/mdstat", "r")) == NULL)
return 0;
while (1) {
More bugs in raidtools: We had a system in which check_active was confusing md8 with md11 in our config. There are several errors in the code related to a global variable named 'cfg' that is almost always local to a function. This patch fixes that so it's local everywhere. More importantly, it fixes the call to check_active that wasn't checking the correct metadevice data structure leading to md8 being confused with md11... Created attachment 74127 [details]
Here is the patch to fix references to cfg (this includes the md10 vs md1 fix)
Created attachment 74704 [details]
here is better fix to the cfg reference problem (includes md10 vs md1 fix)
I've finally managed to get a system set up in which I could test that the fix does indeed work. Thanks! |