Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionCorey Marthaler
2021-09-09 18:08:05 UTC
Description of problem:
Two things here:
1. The name given to vdo on the cmdline should be the default LV name (if possible) when lvm_import_vdo converts it
2. That name should also be an option for conversion, instead of the current long path in the vdoconf.yml file.
[root@hayes-01 ~]# vdo create --force --name lvm_import_vdo_sanity1 --vdoLogicalSize 500G --device /dev/sdc1
Creating VDO lvm_import_vdo_sanity1
The VDO volume can address 1 TB in 929 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.
Starting VDO lvm_import_vdo_sanity1
Starting compression on VDO lvm_import_vdo_sanity1
VDO instance 26 volume is ready at /dev/mapper/lvm_import_vdo_sanity1
[root@hayes-01 ~]# lvm_import_vdo --yes /dev/sdc1
Stopping VDO lvm_import_vdo_sanity1
Converting VDO lvm_import_vdo_sanity1
Opening /dev/disk/by-id/scsi-36d094660575ece002291b9e01bad8691-part1 exclusively
Loading the VDO superblock and volume geometry
Checking the VDO state
Converting the UDS index
Converting the VDO
Conversion completed for '/dev/disk/by-id/scsi-36d094660575ece002291b9e01bad8691-part1': VDO is now offset by 2097152 bytes
Physical volume "/dev/sdc1" successfully created.
Volume group "vdovg" successfully created
WARNING: Logical volume vdovg/vdolvol_vpool not zeroed.
Logical volume "vdolvol_vpool" created.
WARNING: Converting logical volume vdovg/vdolvol_vpool to VDO pool volume WITHOUT formating.
WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
Logical volume "vdolvol" created.
Converted vdovg/vdolvol_vpool to VDO pool volume and created virtual A vdovg/vdolvol VDO volume.
# This LV should be "lvm_import_vdo_sanity1"
[root@hayes-01 ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
vdolvol vdovg vwi-a-v--- 500.00g vdolvol_vpool 0.00
vdolvol_vpool vdovg dwi------- <1.82t 0.31
[root@hayes-01 ~]# vdo create --force --name test_name --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO test_name
The VDO volume can address 1 TB in 929 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.
Starting VDO test_name
Starting compression on VDO test_name
VDO instance 29 volume is ready at /dev/mapper/test_name
[root@hayes-01 ~]# vdo list
test_name
[root@hayes-01 ~]# lvm_import_vdo --yes test_name
lvm_import_vdo: Readlink cannot access device "test_name".
Version-Release number of selected component (if applicable):
lvm2-2.03.12-9.el8 BUILT: Thu Sep 9 08:55:54 CDT 2021
lvm2-libs-2.03.12-9.el8 BUILT: Thu Sep 9 08:55:54 CDT 2021
Comment 3RHEL Program Management
2023-03-09 07:27:56 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: Two things here: 1. The name given to vdo on the cmdline should be the default LV name (if possible) when lvm_import_vdo converts it 2. That name should also be an option for conversion, instead of the current long path in the vdoconf.yml file. [root@hayes-01 ~]# vdo create --force --name lvm_import_vdo_sanity1 --vdoLogicalSize 500G --device /dev/sdc1 Creating VDO lvm_import_vdo_sanity1 The VDO volume can address 1 TB in 929 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. Starting VDO lvm_import_vdo_sanity1 Starting compression on VDO lvm_import_vdo_sanity1 VDO instance 26 volume is ready at /dev/mapper/lvm_import_vdo_sanity1 [root@hayes-01 ~]# lvm_import_vdo --yes /dev/sdc1 Stopping VDO lvm_import_vdo_sanity1 Converting VDO lvm_import_vdo_sanity1 Opening /dev/disk/by-id/scsi-36d094660575ece002291b9e01bad8691-part1 exclusively Loading the VDO superblock and volume geometry Checking the VDO state Converting the UDS index Converting the VDO Conversion completed for '/dev/disk/by-id/scsi-36d094660575ece002291b9e01bad8691-part1': VDO is now offset by 2097152 bytes Physical volume "/dev/sdc1" successfully created. Volume group "vdovg" successfully created WARNING: Logical volume vdovg/vdolvol_vpool not zeroed. Logical volume "vdolvol_vpool" created. WARNING: Converting logical volume vdovg/vdolvol_vpool to VDO pool volume WITHOUT formating. WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA! Logical volume "vdolvol" created. Converted vdovg/vdolvol_vpool to VDO pool volume and created virtual A vdovg/vdolvol VDO volume. # This LV should be "lvm_import_vdo_sanity1" [root@hayes-01 ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert vdolvol vdovg vwi-a-v--- 500.00g vdolvol_vpool 0.00 vdolvol_vpool vdovg dwi------- <1.82t 0.31 [root@hayes-01 ~]# vdo create --force --name test_name --vdoLogicalSize 500G --device /dev/sdd1 Creating VDO test_name The VDO volume can address 1 TB in 929 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. Starting VDO test_name Starting compression on VDO test_name VDO instance 29 volume is ready at /dev/mapper/test_name [root@hayes-01 ~]# vdo list test_name [root@hayes-01 ~]# lvm_import_vdo --yes test_name lvm_import_vdo: Readlink cannot access device "test_name". Version-Release number of selected component (if applicable): lvm2-2.03.12-9.el8 BUILT: Thu Sep 9 08:55:54 CDT 2021 lvm2-libs-2.03.12-9.el8 BUILT: Thu Sep 9 08:55:54 CDT 2021