Bug 1426197 - [RFE] lvm2 is not exposing kernel settings of raid_min/max_recovery_rate
Summary: [RFE] lvm2 is not exposing kernel settings of raid_min/max_recovery_rate
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.169
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: LVM Team
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-23 12:11 UTC by Zdenek Kabelac
Modified: 2023-08-10 15:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?

Attachments (Terms of Use)

Description Zdenek Kabelac 2017-02-23 12:11:26 UTC 
Description of problem:

When raid is created some default invisible and undocumented values are used for some raid settings like raid_max_recovery_rate. There settings do have impact on overall behavior and performance of raid.

lvm2 should be able to expose these values as well as have them configurable
via lvm.conf profiles.

If a user is interested in 'quick' recovery time - he could check existing setting and eventually use higher values (as getting back resilience quickly might be important for some users) so we can have profiles for i.e. quick recovery or  low bandwidth abuse and slow resync times.

In some way it could be similar for 'mirrors' - but I think mirror by 'default' are running with 'highest' possible bandwidth - but we should be probably able to show  kcopy  thresholds as well here.


Version-Release number of selected component (if applicable):
2.02.169

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.