Bug 557053 - mdadm crond script shouldn't run if software raid is not supported by a running kernel
Summary: mdadm crond script shouldn't run if software raid is not supported by a runni...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mdadm
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Doug Ledford
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-20 09:35 UTC by Artem S. Tashkinov
Modified: 2010-04-28 03:09 UTC (History)
1 user (show)

Fixed In Version: initscripts-9.09-1.fc13
Clone Of:
Environment:
Last Closed: 2010-02-19 22:13:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
A patch to eliminate meaningless error messages (411 bytes, application/octet-stream)
2010-01-20 09:35 UTC, Artem S. Tashkinov 		no flags Details
View All

Description Artem S. Tashkinov 2010-01-20 09:35:20 UTC 
Created attachment 385633 [details]
A patch to eliminate meaningless error messages

Description of problem:

from mail:

Date: Wed, 20 Jan 2010 14:09:59 +0500

/etc/cron.weekly/99-raid-check:

grep: /proc/mdstat: No such file or directory


Version-Release number of selected component (if applicable): mdadm-3.0.3-2.fc12.i686


How reproducible: always


Steps to Reproduce:
1. Compile a kernel without software raid
2. Boot into it
3.
  
Actual results: meaningless error messages


Expected results: no error messages


Additional info: patch attached
Comment 1 Doug Ledford 2010-02-19 19:40:38 UTC 
Will be fixed in the next release.
Comment 2 Fedora Update System 2010-04-09 20:12:57 UTC 
mdadm-3.1.2-9.fc13,initscripts-9.09-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/mdadm-3.1.2-9.fc13,initscripts-9.09-1.fc13
Comment 3 Fedora Update System 2010-04-28 03:08:28 UTC 
initscripts-9.09-1.fc13, mdadm-3.1.2-10.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.