2185291 – as vdoLogicalSize 32T approaches 32T limit, the converted LV size reverts to 1.95t

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

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 2185291 - as vdoLogicalSize 32T approaches 32T limit, the converted LV size reverts to 1.95t

Summary: as vdoLogicalSize 32T approaches 32T limit, the converted LV size reverts to ...

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	lvm2
Sub Component:
Version:	8.7
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	LVM Team
QA Contact:	Zdenek Kabelac
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2023-04-07 19:43 UTC by Corey Marthaler
Modified:	2023-09-23 18:51 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-23 18:51:52 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-8321	0	None	Migrated	None	2023-09-23 18:52:00 UTC
Red Hat Issue Tracker	RHELPLAN-154248	0	None	None	None	2023-04-07 19:43:37 UTC

Description Corey Marthaler 2023-04-07 19:43:07 UTC

Description of problem:

This appears similar/related to bug 1996227.


# 30T

SCENARIO - large_vdo_logical_size_convert_to_lvm:  Test the basic conversion of a large (4t) logical sized existent vdo volume to lvm (1996227)
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 30T --device /dev/sda1
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 1 TB in 998 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 6 volume is ready at /dev/mapper/lvm_import_vdo_sanity

lvm_import_vdo --yes /dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1
WARNING: Heartbeat did not respond at start of command.  Check btimed service on remote host
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
      Opening /dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-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-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1': VDO is now offset by 2097152 bytes
  Physical volume "/dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1" successfully created.
  Volume group "vdovg" successfully created
  Logical volume "vdolvol_vpool" created.
  WARNING: Logical volume vdovg/vdolvol_vpool not zeroed.
  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 vdovg/vdolvol VDO volume.
Conversion size:30.00t

[root@virt-247 ~]# lvs -a -o +devices
  LV                    VG            Attr       LSize   Pool          Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices               
  vdolvol               vdovg         vwi-a-v---  30.00t vdolvol_vpool        0.00                                    vdolvol_vpool(0)      
  vdolvol_vpool         vdovg         dwi-------   1.95t                      0.27                                    vdolvol_vpool_vdata(0)
  [vdolvol_vpool_vdata] vdovg         Dwi-ao----   1.95t                                                              /dev/sda1(0)          
 


# 31T

SCENARIO - large_vdo_logical_size_convert_to_lvm:  Test the basic conversion of a large (4t) logical sized existent vdo volume to lvm (1996227)
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 31T --device /dev/sda1
WARNING: Heartbeat did not respond at start of command.  Check btimed service on remote host
Creating VDO lvm_import_vdo_sanity
      Found existing signature on /dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1 at offset 536: LABEL="(null)" UUID="KqJMTR-VKYa-zg1i-2c05-6kJD-RVC5-dtWNuG" TYPE="LVM2_member" USAGE="raid".
      Formatting device already containing a known signature.
      The VDO volume can address 1 TB in 998 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 8 volume is ready at /dev/mapper/lvm_import_vdo_sanity

lvm_import_vdo --yes /dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
      Opening /dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-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-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1': VDO is now offset by 2097152 bytes
  Physical volume "/dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1" successfully created.
  Volume group "vdovg" successfully created
  Logical volume "vdolvol_vpool" created.
  WARNING: Logical volume vdovg/vdolvol_vpool not zeroed.
  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 vdovg/vdolvol VDO volume.
Conversion size:31.00t

[root@virt-247 ~]# lvs -a -o +devices
  LV                    VG            Attr       LSize   Pool          Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices               
  vdolvol               vdovg         vwi-a-v---  31.00t vdolvol_vpool        0.00                                    vdolvol_vpool(0)      
  vdolvol_vpool         vdovg         dwi-------   1.95t                      0.27                                    vdolvol_vpool_vdata(0)
  [vdolvol_vpool_vdata] vdovg         Dwi-ao----   1.95t                                                              /dev/sda1(0)          



# 32T

SCENARIO - large_vdo_logical_size_convert_to_lvm:  Test the basic conversion of a large (4t) logical sized existent vdo volume to lvm (1996227)
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 32T --device /dev/sda1
WARNING: Heartbeat did not respond at start of command.  Check btimed service on remote host
Creating VDO lvm_import_vdo_sanity
      Found existing signature on /dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1 at offset 536: LABEL="(null)" UUID="8FJcmZ-bMwj-5Vjh-aXih-34RB-owru-9WGtkF" TYPE="LVM2_member" USAGE="raid".
      Formatting device already containing a known signature.
      The VDO volume can address 1 TB in 998 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 10 volume is ready at /dev/mapper/lvm_import_vdo_sanity

lvm_import_vdo --yes /dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
      Opening /dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-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-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1': VDO is now offset by 2097152 bytes
  Physical volume "/dev/disk/by-id/scsi-1LIO-ORGcluster147063-d:d6011f2b-3f53-48eb-8e8d-8e8bc6bd70c2-part1" successfully created.
  Volume group "vdovg" successfully created
  Logical volume "vdolvol_vpool" created.
  WARNING: Logical volume vdovg/vdolvol_vpool not zeroed.
  Volume too large (32.00 TiB) for extent size 8.00 KiB. Upper limit is less than <32.00 TiB.
  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 vdovg/vdolvol VDO volume.
Conversion size:1.95t

[root@virt-247 ~]# lvs -a -o +devices
  LV                    VG            Attr       LSize   Pool          Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices               
  vdolvol               vdovg         vwi-a-v---   1.95t vdolvol_vpool        0.00                                    vdolvol_vpool(0)      
  vdolvol_vpool         vdovg         dwi-------   1.95t                      0.27                                    vdolvol_vpool_vdata(0)
  [vdolvol_vpool_vdata] vdovg         Dwi-ao----   1.95t                                                              /dev/sda1(0)          


Version-Release number of selected component (if applicable):
kernel-4.18.0-477.7.1.el8_8    BUILT: Thu Mar 30 16:50:52 CEST 2023
lvm2-2.03.14-9.el8    BUILT: Thu Dec  8 17:40:55 CET 2022
lvm2-libs-2.03.14-9.el8    BUILT: Thu Dec  8 17:40:55 CET 2022


How reproducible:
Everytime

Comment 2 Zdenek Kabelac 2023-09-20 09:42:53 UTC

Please retest with latest instance of lvm_import_vdo script. It should be solved with the same script as in bug 2233901.

Comment 4 RHEL Program Management 2023-09-23 18:51:04 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-23 18:51:52 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Note You need to log in before you can comment on or make changes to this bug.