Bug 113974
Summary: | mdadm examine shows device state as dirty, no-errors | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Frank LeFevre <lefevre> |
Component: | mdadm | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | billgo, bjohnson, laroche, markwiz, mpeschke |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | s390 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-01-26 14:15:53 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
Frank LeFevre
2004-01-20 21:03:01 UTC
This looks like you are performing the mdadm -E on the device while the array is still live. The array state is always dirty, no errors until either an error occurs or the array is switched to readonly mode or stopped completely. The only time the state should be clean, no errors is on a read-only or completely stopped array. So, if you are seeing this on a currently running array, then please close this bug report as NOTABUG and if the array is not running then make note of that in this bug report. I was offsite yesterday at LinuxWorld and today our machine is down for hardware service. Will try as soon as it's back up. Thanks. Array was active. Once array was stopped, the display showed clean. Thanks. |