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.

Bug 2005003

Summary: vdoimport conversion tool need to increment the default VG name used when one is not given [rhel-8.6.0]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: VDO QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: urgent CC: agk, awalsh, cmarthal, heinzm, jbrassow, lmiksik, mcsontos, prajnoha, zkabelac
Version: 8.5Keywords: Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.03.14-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1986915 Environment:
Last Closed: 2022-05-10 15:21:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1986915    
Bug Blocks:    

Comment 1 Zdenek Kabelac 2021-09-22 14:34:16 UTC 
Upstream fixed in 2.03.14
Comment 3 Corey Marthaler 2021-11-03 03:42:05 UTC 
Marking Verified:Tested in the latest rpms.

kernel-4.18.0-348.4.el8.kpq0    BUILT: Wed Oct 27 15:00:32 CDT 2021
lvm2-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-libs-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-dbusd-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:48 CDT 2021



SCENARIO - [attempt_in_use_lv_name_lvm_import_vdo_convert]
Test the proceedure for converting a vdo volume when the default lv names are already in use (1986915)
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 928 GB in 464 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_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 152 volume is ready at /dev/mapper/lvm_import_vdo_sanity

vgcreate vdovg /dev/sdc1
  Physical volume "/dev/sdc1" successfully created.
  Volume group "vdovg" successfully created
lvcreate --yes -L 500M -n vdolvol_vpool vdovg
  Logical volume "vdolvol_vpool" created.
vgcreate vdovg1 /dev/sdb1
  Physical volume "/dev/sdb1" successfully created.
  Volume group "vdovg1" successfully created
lvcreate --yes -L 500M -n vdolvol vdovg1
  Logical volume "vdolvol" created.

lvm_import_vdo --yes /dev/disk/by-id/scsi-36d094660650d1e0022bd29f31e631f3e-part1
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
      Opening /dev/disk/by-id/scsi-36d094660650d1e0022bd29f31e631f3e-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-36d094660650d1e0022bd29f31e631f3e-part1': VDO is now offset by 2097152 bytes
  Physical volume "/dev/disk/by-id/scsi-36d094660650d1e0022bd29f31e631f3e-part1" successfully created.
  Volume group "vdovg2" successfully created
  Logical volume "vdolvol_vpool" created.
  WARNING: Logical volume vdovg2/vdolvol_vpool not zeroed.
  WARNING: Converting logical volume vdovg2/vdolvol_vpool to VDO pool volume WITHOUT formating.
  WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
  Logical volume "vdolvol" created.
  Converted vdovg2/vdolvol_vpool to VDO pool volume and created virtual vdovg2/vdolvol VDO volume.

lvremove -f vdovg2
  Logical volume "vdolvol" successfully removed.
vgremove -f vdovg2
  Volume group "vdovg2" successfully removed
pvremove /dev/sdd1
  Labels on physical volume "/dev/sdd1" successfully wiped.
lvmdevices -y --deldev /dev/sdd1
lvremove -f vdovg
  Logical volume "vdolvol_vpool" successfully removed.
vgremove -f vdovg
  Volume group "vdovg" successfully removed
pvremove /dev/sdc1
  Labels on physical volume "/dev/sdc1" successfully wiped.
lvmdevices -y --deldev /dev/sdc1
lvremove -f vdovg1
  Logical volume "vdolvol" successfully removed.
vgremove -f vdovg1
  Volume group "vdovg1" successfully removed
pvremove /dev/sdb1
  Labels on physical volume "/dev/sdb1" successfully wiped.
lvmdevices -y --deldev /dev/sdb1
Comment 7 Corey Marthaler 2021-11-16 18:40:47 UTC 
Marking Verified in the latest rpms.

kernel-4.18.0-348.4.el8.kpq0    BUILT: Wed Oct 27 15:00:32 CDT 2021
lvm2-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-libs-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021


SCENARIO - attempt_in_use_lv_name_lvm_import_vdo_convert:  Test the procedure for converting a second vdo volume when the default name is already in use (1986915) 
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO lvm_import_vdo_sanity
      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_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 14 volume is ready at /dev/mapper/lvm_import_vdo_sanity
vgcreate vdovg /dev/sdc1
  Physical volume "/dev/sdc1" successfully created.
  Volume group "vdovg" successfully created
lvcreate --yes -L 500M -n vdolvol_vpool vdovg
  Logical volume "vdolvol_vpool" created.
vgcreate vdovg1 /dev/sdb1
  Physical volume "/dev/sdb1" successfully created.
  Volume group "vdovg1" successfully created
lvcreate --yes -L 500M -n vdolvol vdovg1
  Logical volume "vdolvol" created.

lvm_import_vdo --yes /dev/disk/by-id/scsi-36d094660575ece002291ba5c230d16c6-part1
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
      Opening /dev/disk/by-id/scsi-36d094660575ece002291ba5c230d16c6-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-36d094660575ece002291ba5c230d16c6-part1': VDO is now offset by 2097152 bytes
  Physical volume "/dev/disk/by-id/scsi-36d094660575ece002291ba5c230d16c6-part1" successfully created.
  Volume group "vdovg2" successfully created
  WARNING: Logical volume vdovg2/vdolvol_vpool not zeroed.
  Logical volume "vdolvol_vpool" created.
  WARNING: Converting logical volume vdovg2/vdolvol_vpool to VDO pool volume WITHOUT formating.
  WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
  Logical volume "vdolvol" created.
  Converted vdovg2/vdolvol_vpool to VDO pool volume and created virtual vdovg2/vdolvol VDO volume.
Comment 9 errata-xmlrpc 2022-05-10 15:21:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (lvm2 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2038