Bug 1426197

Summary:	[RFE] lvm2 is not exposing kernel settings of raid_min/max_recovery_rate
Product:	[Community] LVM and device-mapper	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	LVM Team <lvm-team>
lvm2 sub component:	Mirroring and RAID	QA Contact:	cluster-qe <cluster-qe>
Status:	NEW ---	Docs Contact:
Severity:	unspecified
Priority:	low	CC:	agk, heinzm, jbrassow, msnitzer, prajnoha, zkabelac
Version:	2.02.169	Keywords:	Triaged
Target Milestone:	---	Flags:	rule-engine: lvm-technical-solution? rule-engine: lvm-test-coverage?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 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: