'lvm_import_vdo' does not complete for converting very big size vdo devices

Solution In Progress - Updated -

Issue

  • lvm_import_vdo fails to create vg on very big size vdo devices and makes the vdo device to be converted into inaccessible state.
  • Creating non-lvm vdo device to lvm based vdo device using lvm_import_vdo command fails in creating the VG.
# lvm_import_vdo --name vgname/lvname /dev/disk/by-id/scsi-36b07b2512345678efabcdf11d1234566
Convert VDO device "/dev/disk/by-id/scsi-36b07b2512345678efabcdf11d1234566" to VDO LV "vgname/lvname"? [y|N]: Yes
Stopping VDO repo
vdo: WARNING - VDO service repo already stopped
Converting VDO repo
      Opening /dev/disk/by-id/scsi-36b07b2512345678efabcdf11d1234566 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-36b07b2512345678efabcdf11d1234566': VDO is now offset by 2097152 bytes
  Physical volume "/dev/disk/by-id/scsi-36b07b2512345678efabcdf11d1234566" successfully created.
  PV /dev/sda too large for extent size 4.00 KiB.
  Format-specific setup of physical volume '/dev/sda' failed.
  PV /dev/sda cannot be added to VG vgname.
lvm_import_vdo: Creation of VG "vgname" failed, while VDO header has been already moved!

Environment

  • Red Hat Enterprise Linux 8
    • lvm vdo

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content