Bug 969214
Summary: | LVM RAID: Add ability to throttle sync operations for RAID LVs | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jonathan Earl Brassow <jbrassow> |
Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
lvm2 sub component: | Default / Unclassified | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, msnitzer, nperic, prajnoha, prockai, thornber, zkabelac |
Version: | 7.0 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-13 10:48:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jonathan Earl Brassow
2013-05-30 22:11:01 UTC
Testing should include: 1) ensuring that '--maxrecoveryrate <rate>' - found in lvcreate and lvchange - can be used to limit sync I/O so as not to crowd-out nominal I/O 2) that '--minrecoveryrate <rate>' can be used to ensure that sync I/O achieves a minimum throughput even when heavy nominal I/O is present. N.B. The rates specified cannot be perfectly guaranteed. While the result is "best-effort", the affects should be close. Patch commited upstream: commit 562c678ee23e76b675a8f4682bd6d2447d1d0de7 Author: Jonathan Brassow <jbrassow> Date: Fri May 31 11:25:52 2013 -0500 DM RAID: Add ability to throttle sync operations for RAID LVs. This patch adds the ability to set the minimum and maximum I/O rate for sync operations in RAID LVs. The options are available for 'lvcreate' and 'lvchange' and are as follows: --minrecoveryrate <Rate> [bBsSkKmMgG] --maxrecoveryrate <Rate> [bBsSkKmMgG] The rate is specified in size/sec/device. If a suffix is not given, kiB/sec/device is assumed. Setting the rate to 0 removes the preference. Both lvcreate and lvchange honor --maxrecovery rate settings. When creating a lot of raid10 volumes, the creation slows down substantially after a few LVs. When 'maxrecoveryrate' is set the creation is almost instant and the synchornisation goes slower. However there is a same issue as in RHEL 6, after using lvchange on an LV to modify maxrecovery rate the percentage displayed drops (for low percentages all the way to 0.00) Tested with lvm2-2.02.103-5.el7.x86_64 Marking VERIFIED on RHEL7 with: lvm2-2.02.105-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014 lvm2-libs-2.02.105-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014 lvm2-cluster-2.02.105-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014 device-mapper-1.02.84-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014 device-mapper-libs-1.02.84-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014 device-mapper-event-1.02.84-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014 device-mapper-event-libs-1.02.84-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014 device-mapper-persistent-data-0.3.0-1.el7 BUILT: Fri Mar 28 13:42:24 CET 2014 This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |