Bug 832749
Summary: | [abrt] mdadm-3.2.3-6.fc17: __GI_raise: Process /usr/sbin/mdadm was killed by signal 6 (SIGABRT) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Frank Crawford <frank> | ||||||||
Component: | mdadm | Assignee: | Jes Sorensen <Jes.Sorensen> | ||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 17 | CC: | agk, cks-rhbugzilla, dledford, Jes.Sorensen | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:36b1722fbbd0a5aebf80ed807dd17f026293b8ac | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2012-06-26 14:38:12 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
Frank Crawford
2012-06-17 07:05:44 UTC
Created attachment 592377 [details]
File: backtrace
Created attachment 592378 [details]
File: coredump
Created attachment 592379 [details]
File: var_log_messages
I believe this problem may be fixed by the mdadm-3.2.5 update found in updates testing. https://admin.fedoraproject.org/updates/FEDORA-2012-8988/mdadm-3.2.5-1.fc17 or run 'yum --enablerepo=updates-testing install mdadm' If you see this again after updating to mdadm-3.2.5, please make sure to install the debuginfo package and report the backtrace with that. Thanks, Jes The updates-testing mdadm fixed what I think is this problem for me. In my case, mdadm monitoring would die with a SIGABRT shortly after the first scan finished in the weekly 'check all RAID arrays' cron job. I installed the updated mdadm (and restarted mdmonitor.service), ran /usr/sbin/raid-check by hand, and mdadm monitoring is still alive and happy. Excellent! I was suspecting that could be the case as I know there is a fix for mdmon crashes in that update. FWIW I just poushed mdadm-3.2.5-3 out however the fixes are minor. I'll close this bug since it seems to work for you. If you hit the issue again please reopen it or file a new bug. Cheers, Jes |