Bug 1895095

Summary: VDO creation should select better values for bigger sized volumes
Product: [Community] LVM and device-mapper Reporter: Zdenek Kabelac <zkabelac>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: Other QA Contact: cluster-qe <cluster-qe>
Status: NEW --- Docs Contact:
Severity: unspecified    
Priority: unspecified CC: agk, heinzm, jbrassow, msnitzer, prajnoha, zkabelac
Version: unspecifiedFlags: pm-rhel: lvm-technical-solution?
pm-rhel: lvm-test-coverage?
Target Milestone: ---   
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 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.