Bug 65560
Summary: | RFE: Raid rebuild IO capacity needs improving, also no rebuild on mkraid | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Cristian Gafton <gafton> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 7.3 | CC: | mingo, msf, msw |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-07 18:34:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Cristian Gafton
2002-05-27 16:45:51 UTC
short term fix is to reduce the max speed by an order of magnitude; longer term the speed should be a percentage of IO capacity or be marked "low priority" where all other IO gets precedence. *** Bug 65597 has been marked as a duplicate of this bug. *** It would be beneficial if anaconda would "slow down" the raid rebuild during the installation by inserting a lower value in speed_limit_max before the raid devices are rebuilt. Also, on the "nice to have" list, having a way to tell raid that it doesn't really need to do a full resync of a freshly created array (not unless it is dependent on having exactly the same bitcopy on all drives as opposed to just syncing superblocks...) The max speed issue is fixed for the next build; changing this to an RFE bug since the points are valid and I'd like to address them |