Bug 2108227

Summary: vdo_check_point_frequency alteration is not supported even though it's listed as a part of RFE 2100608
Product: Red Hat Enterprise Linux 8 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: VDO QA Contact: cluster-qe <cluster-qe>
Status: ASSIGNED --- Docs Contact:
Severity: low    
Priority: unspecified CC: agk, awalsh, heinzm, jbrassow, prajnoha, zkabelac
Version: 8.7Keywords: FutureFeature
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
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 Corey Marthaler 2022-07-18 16:06:19 UTC
Description of problem:
[root@hayes-02 ~]# lvcreate --yes --type linear -n vdo_pool  -L 5G vdo_sanity  
  Logical volume "vdo_pool" created.

[root@hayes-02 ~]# lvconvert --yes --type vdo-pool -n vdo_lv --vdosettings 'vdo_check_point_frequency=1' -V 20G vdo_sanity/vdo_pool
lvconvert: unrecognized option '--vdosettings'
  Error during parsing of command line.

[root@hayes-02 ~]# lvconvert --yes --type vdo-pool -n vdo_lv -V 20G vdo_sanity/vdo_pool
  WARNING: Converting logical volume vdo_sanity/vdo_pool to VDO pool volume with formating.
  THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
    The VDO volume can address 2 GB in 1 data slab.
    It can grow to address at most 16 TB of physical storage in 8192 slabs.
    If a larger maximum size might be needed, use bigger slabs.
  Logical volume "vdo_lv" created.
  Converted vdo_sanity/vdo_pool to VDO pool volume and created virtual vdo_sanity/vdo_lv VDO volume.

[root@hayes-02 ~]# lvconvert --vdosettings 'vdo_check_point_frequency=1' vdo_sanity/vdo_pool
lvconvert: unrecognized option '--vdosettings'
  Error during parsing of command line.




"Comment #15

'vdo_check_point_frequency' is problematic - it's 'gone' from current version of vdoformat tooling - so here lvm2 will need to 'ignore' any changes to this setting other then value 0  - so this is current bug in lvm2 handling that needs a fix."



lvm2-2.03.14-4.el8    BUILT: Wed Jun 15 17:14:34 CDT 2022
lvm2-libs-2.03.14-4.el8    BUILT: Wed Jun 15 17:14:34 CDT 2022