# Both of these LVM versions work
kernel-5.14.0-522.el9    BUILT: Sun Oct 20 03:53:48 PM CEST 2024
lvm2-2.03.24-2.el9    BUILT: Wed Aug  7 09:41:45 PM CEST 2024
lvm2-libs-2.03.24-2.el9    BUILT: Wed Aug  7 09:41:45 PM CEST 2024
[** AND **]
lvm2-2.03.27-1.el9    BUILT: Wed Oct  9 12:38:05 PM CEST 2024
lvm2-libs-2.03.27-1.el9    BUILT: Wed Oct  9 12:38:05 PM CEST 2024
  
[root@virt-258 ~]# lvcreate --yes --type linear -n vdo_pool  -L 20G vdo_sanity  
  Wiping vdo signature on /dev/vdo_sanity/vdo_pool.
  Logical volume "vdo_pool" created.
[root@virt-258 ~]# lvconvert --yes --type vdo-pool -n vdo_lv  -V 100G vdo_sanity/vdo_pool
  WARNING: Converting logical volume vdo_sanity/vdo_pool to VDO pool volume with formatting.
  THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
    The VDO volume can address 16 GB in 8 data slabs, each 2 GB.
    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@virt-258 ~]# lvs -a -o +devices
  LV               VG            Attr       LSize   Pool     Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices          
  vdo_lv           vdo_sanity    vwi-a-v--- 100.00g vdo_pool        0.00                                    vdo_pool(0)      
  vdo_pool         vdo_sanity    dwi-------  20.00g                 20.05                                   vdo_pool_vdata(0)
  [vdo_pool_vdata] vdo_sanity    Dwi-ao----  20.00g                                                         /dev/sdb(0)      
[root@virt-258 ~]# lvconvert --yes --type raid1 -m 2 vdo_sanity/vdo_pool_vdata
  Logical volume vdo_sanity/vdo_pool_vdata successfully converted.
 
 
# The latest LVM version version fails.
kernel-5.14.0-522.el9    BUILT: Sun Oct 20 03:53:48 PM CEST 2024
lvm2-2.03.28-1.el9    BUILT: Tue Nov  5 01:24:44 PM CET 2024
lvm2-libs-2.03.28-1.el9    BUILT: Tue Nov  5 01:24:44 PM CET 2024
 
 
[root@virt-256 ~]# lvcreate --yes --type linear -n vdo_pool  -L 20G vdo_sanity  
  Logical volume "vdo_pool" created.
[root@virt-256 ~]# lvconvert --yes --type vdo-pool -n vdo_lv  -V 100G vdo_sanity/vdo_pool
  WARNING: Converting logical volume vdo_sanity/vdo_pool to VDO pool volume with formatting.
  THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
    The VDO volume can address 16 GB in 8 data slabs, each 2 GB.
    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@virt-256 ~]# lvs -a -o +devices
  LV               VG         Attr       LSize   Pool     Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices          
  vdo_lv           vdo_sanity vwi-a-v--- 100.00g vdo_pool        0.00                                    vdo_pool(0)      
  vdo_pool         vdo_sanity dwi-------  20.00g                 20.05                                   vdo_pool_vdata(0)
  [vdo_pool_vdata] vdo_sanity Dwi-ao----  20.00g                                                         /dev/sdb(0)      
[root@virt-256 ~]# lvconvert --yes --type raid1 -m 2 vdo_sanity/vdo_pool_vdata
  Duplicate LV name vdo_pool_vdata_rimage_1 detected.