RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 819943 - RFE: Limit raid-check cron to a maximum number of concurrent checks
Summary: RFE: Limit raid-check cron to a maximum number of concurrent checks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mdadm
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Jes Sorensen
QA Contact: XiaoNi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-08 16:43 UTC by Orion Poplawski
Modified: 2013-11-21 12:03 UTC (History)
4 users (show)

Fixed In Version: mdadm-3.2.6-3.el6
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 12:03:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch to add MAXCONCURRENT (2.48 KB, patch)
2012-05-08 16:43 UTC, Orion Poplawski 		no flags Details | Diff
Patch to add MAXCONCURRENT to raid-check (2.14 KB, patch)
2012-05-30 15:19 UTC, Orion Poplawski 		no flags Details | Diff
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1643 0 normal SHIPPED_LIVE mdadm bug fix and enhancement update 2013-11-20 21:53:30 UTC

Description Orion Poplawski 2012-05-08 16:43:54 UTC 
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
Comment 2 Jes Sorensen 2012-05-09 07:43:44 UTC 
Orion,

This is definitely too late for 6.3, but lets consider it for 6.4.

In the mean time I recommend we push it into Fedora first and let it soak
there for a bit first.

I will clone this BZ into a Fedora one and push it there first, if that is
ok with you.

Cheers,
Jes
Comment 3 Jes Sorensen 2012-05-30 06:59:16 UTC 
Orion,

How did you get along with the testing?

Thanks,
Jes
Comment 4 Orion Poplawski 2012-05-30 15:11:52 UTC 
Doesn't work, it checks the same array each time:

May 27 01:00:01 alexandria2 kernel: md: data-check of RAID array md1
May 27 01:00:01 alexandria2 kernel: md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
May 27 01:00:01 alexandria2 kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check.
May 27 01:00:01 alexandria2 kernel: md: using 128k window, over a total of 77943740k.
May 27 01:27:51 alexandria2 kernel: md: md1: data-check done.
May 27 01:28:08 alexandria2 kernel: md: data-check of RAID array md1
May 27 01:28:08 alexandria2 kernel: md: minimum _guaranteed_  speed: 1000 KB/sec/disk.          
May 27 01:28:08 alexandria2 kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check.
May 27 01:28:08 alexandria2 kernel: md: using 128k window, over a total of 77943740k.           
May 27 01:56:09 alexandria2 kernel: md: md1: data-check done.
May 27 01:56:15 alexandria2 kernel: md: data-check of RAID array md1

...

Looks like I'm clobberring some global variables.
Comment 5 Orion Poplawski 2012-05-30 15:19:26 UTC 
Created attachment 587768 [details]
Patch to add MAXCONCURRENT to raid-check
Comment 6 Jes Sorensen 2012-05-30 15:55:35 UTC 
Orion,

Thanks for the update - the new version you attached works as expected?

Cheers,
Jes
Comment 7 Orion Poplawski 2012-05-30 15:58:36 UTC 
No idea - need to test it.
Comment 8 Jes Sorensen 2012-05-30 15:59:30 UTC 
Ok, I'll wait for feedback from you before I start touching it.

Cheers,
Jes
Comment 9 Orion Poplawski 2012-05-31 21:30:42 UTC 
Updated patch appears to work as expected, at least for the MAXCONCURRENT=1 case.
Comment 10 Tom Lavigne 2012-09-07 15:23:34 UTC 
This request was evaluated by Red Hat Product Management for 
inclusion in the current release of Red Hat Enterprise Linux.
Since we are unable to provide this feature at this time,  
it has been proposed for the next release of 
Red Hat Enterprise Linux.
Comment 11 Jes Sorensen 2013-05-03 08:20:47 UTC 
Ok this has been in Fedora for a long time now and nobody complained, so
lets have a look for 6.5.

Jes
Comment 16 XiaoNi 2013-10-23 08:24:19 UTC 
Hi All

   I have reproduced this problem. The steps as follows:
   1. create two raid5 
   Personalities : [raid6] [raid5] [raid4] [raid1] [raid10] [raid0] 
   md1 : active raid5 sdf[3] sde[1] sdd[0]
      4191232 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
      
   md0 : active raid5 sdi[3] sdh[1] sdg[0]
      4191232 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

   2. run /usr/sbin/raid-check when MAXCONCURRENT=0
      At this condition, md0 and md1 do the check at the same time. the devices under the raid all have read io.

   3. run /usr/sbin/raid-check when MAXCONCURRENT=1
      At this condition, only one of the two raid do the check. 

   So, set verified.
Comment 17 errata-xmlrpc 2013-11-21 12:03:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1643.html
Note You need to log in before you can comment on or make changes to this bug.