Bug 748986
Summary: | mdadm starts resync on imsm raid even in Normal state | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Bieringer <pb> | |
Component: | mdadm | Assignee: | Jes Sorensen <Jes.Sorensen> | |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 15 | CC: | agk, dledford, Jes.Sorensen, mbroz, ncjeffgus | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | i686 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 753335 (view as bug list) | Environment: | ||
Last Closed: | 2012-07-11 07:31:48 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
Peter Bieringer
2011-10-25 18:57:48 UTC
Does this happen both if you are using the RAID for booting from and/or if you have the RAID as a secondary device and boot off a regular partition? The RAID is my primary device, I can't easily configure it as second device...no other bootable disks in there. But it looks like it has to do with the shutdown procedure. Yesterday, I need to poweroff via Alt-Sysrq (hanging during "unmount", probably related to autofs problem). Now booting today (BIOS-Status: Normal), no resync was triggered. Rebooting now again will result in resync (array detected as "not clean"). My system is too fast to follow last messages before booting, but I thought I have seen on Alt-Sysrq-Poweroff something like "raid status stored", while on reboot, nothing such was seen. Interesting - I was wondering if it was related to shutdown. The problem with BIOS RAID is that the kernel cannot do the full shutdown on it's own, so if something is hanging and preventing mdadm/mdmon from doing their job, it could result in some of the RAID metadata not being written out as it should. So, next normal shutdown triggered and power-on again -> resync starts again. For me it looks like only Alt-Sysrq-Poweroff will leave a synced RAID in proper state for next power-on. Normal power-off or reboot won't. Any suggestions for debugging this deeper? I am also having this issue on Fedora 16. The system was running Fedora 15 and was upgraded to 16. Something happen in Fedora 15 that was causing it to not boot correctly. I went ahead and upgraded to 16. It went smooth except for this issue. Fedora 15 has reached end of life, so we'll continue to investigate this problem in the Fedora 17 bugzilla #753335 |