1895095 – VDO creation should select better values for bigger sized volumes

Bug 1895095 - VDO creation should select better values for bigger sized volumes

Summary: VDO creation should select better values for bigger sized volumes

Keywords:
Status:	NEW
Alias:	None
Product:	LVM and device-mapper
Classification:	Community
Component:	lvm2
Sub Component:
Version:	unspecified
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Target Release:	---
Assignee:	Zdenek Kabelac
QA Contact:	cluster-qe
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2020-11-05 18:17 UTC by Zdenek Kabelac
Modified:	2023-08-10 15:41 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
Flags:	pm-rhel: lvm-technical-solution? pm-rhel: lvm-test-coverage?

Attachments	(Terms of Use)

Description Zdenek Kabelac 2020-11-05 18:17:20 UTC

ATM lvm2 doesn't do any calculation for selecting better values for
VDO slab size and eventually influence  sparse/dense index selection
based on available system resource.

For sizes over 16TiB the default VDO slab size doesn't even allow to create VDOPoolLV.

lvm2 should scale up slab size if it's not defined by user.

Heuristic similar to selection of chunksize for thin-pool needs to be introduced to pick more usable values.

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