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:14:54 UTC
Description of problem:
[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 30 volume is ready at /dev/mapper/test_name
# No
[root@hayes-01 ~]# lvm_import_vdo /dev/sdd1
Convert VDO device "/dev/sdd1" to VDO LV "vdovg/vdolvol"? [y|N]: No
[root@hayes-01 ~]# echo $?
0
# ^C
[root@hayes-01 ~]# lvm_import_vdo /dev/sdd1
Convert VDO device "/dev/sdd1" to VDO LV "vdovg/vdolvol"? [y|N]: No
[root@hayes-01 ~]# echo $?
2
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
Description of problem: [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 30 volume is ready at /dev/mapper/test_name # No [root@hayes-01 ~]# lvm_import_vdo /dev/sdd1 Convert VDO device "/dev/sdd1" to VDO LV "vdovg/vdolvol"? [y|N]: No [root@hayes-01 ~]# echo $? 0 # ^C [root@hayes-01 ~]# lvm_import_vdo /dev/sdd1 Convert VDO device "/dev/sdd1" to VDO LV "vdovg/vdolvol"? [y|N]: No [root@hayes-01 ~]# echo $? 2 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