Hide Forgot
+++ This bug was initially created as a clone of Bug #819943 +++ Created attachment 583043 [details] Patch to add MAXCONCURRENT Description of problem: I've got some disk servers with 4 9TB radi5 arrays. raid-check puts too much of a load on them. The attached patch (to mdadm-3.2.2-9) allows the use of a MAXCONCURENT option that limits the number of concurrently checked arrays. This is a quick port of the EL5 version. Will test it out this weekend. Version-Release number of selected component (if applicable): mdadm-3.2.2-9
Created attachment 583189 [details] Patch to add MAXCONCURRENT variable to raid-check
mdadm-3.2.5-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mdadm-3.2.5-3.fc17
mdadm-3.2.5-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.5-3.fc16
Package mdadm-3.2.5-3.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mdadm-3.2.5-3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-9931/mdadm-3.2.5-3.fc16 then log in and leave karma (feedback).
mdadm-3.2.5-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
mdadm-3.2.5-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.