Bug 169443
Summary: | lsraid and /proc/mdstat reports different statuses on arrays | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Dan Fruehauf <danfr> |
Component: | raidtools | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
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-26 22:25: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
Dan Fruehauf
2005-09-28 13:18:57 UTC
First, lsraid is part of the deprecated raidtools package and likely will not be updated regardless of whether there is a bug there or not. Mdadm is the preferred tool to use, and mdadm -E --brief will probably give you what you are looking for. Now, the issue of lsraid not seeing the spare is probably because the drive hasn't started the resync process yet. Since md1 is already resyncing, the process of adding sdc3 to md2 would be delayed and therefore the disk would not be registered as an active spare yet. As to which to trust? They are both correct. The mdstat file shows the current kernel state. The kernel knows about the new spare disks, but isn't doing anything with them yet. When lsraid queries the disk array, it doesn't see the spare because the spare isn't live yet. The oops on shutting down the md2 array is another matter entirely and I believe I already know what that problem is. I believe you'll find that the oops has already been reported in bz #134736. Since I don't see a bug in this report, other than the oops which is already reported elsewhere, I'm closing this bug report out. Thank you for the report and please add yourself to the above mentioned bugzilla if you would like to be kept abreast of when the "shutting down a raid1 array while a rebuild is taking place" bug gets fixed. |