Description of problem: I have a system with 24 2TB disks in RAID-10 volume. Its raid check takes 11 hours on a totally idle system with manually increased /sys/block/md*/md/sync_speed_{min,max}, and under moderate load it takes over a day. For me it is not feasible to have the array being checked weekly. I would suggest making /etc/cron.weekly/99-raid-check a script in /usr/sbin, and a /etc/cron.d/raid-check crontab with the %config attribute. It would allow users to set up their own prefered frequency and start time of raid checks. I think for 99-raid-check we don't need the benefits of anacron, which /etc/cron.weekly provides. Quite opposite is true: anacron makes the problem worse, because 99-raid-check is started at random times, and after the reboot it can be started even outside the weekend. Version-Release number of selected component (if applicable): mdadm-3.1.3-0.git20100804.2.fc14.x86_64
Good suggestion. This is going into the mdadm-3.1.4 package. Please test to make sure it meets your needs.
mdadm-3.1.5-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mdadm-3.1.5-1.fc15
Package mdadm-3.1.5-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mdadm-3.1.5-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/mdadm-3.1.5-1.fc15 then log in and leave karma (feedback).
Package mdadm-3.1.5-2.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mdadm-3.1.5-2.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/mdadm-3.1.5-2.fc15 then log in and leave karma (feedback).
mdadm-3.1.5-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.