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 2139930

Summary: going over the "Maximal supported VDO virtual size" should fail
Product: Red Hat Enterprise Linux 9 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: VDO QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: unspecified CC: agk, awalsh, cmackows, heinzm, jbrassow, prajnoha, zkabelac
Version: 9.2Keywords: Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.03.17-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:23:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2022-11-03 21:12:47 UTC 
Description of problem:

# rhel8.7 (and 9.1 I believe)
[root@hayes-01 ~]# lvcreate --yes --type vdo -n vdo_lv  -L 10G vdo_sanity -V 4503599627371008b
  Rounding up size to full physical extent 4.00 PiB
  VDO logical size is by 5120KiB bigger then limit 4096TiB.
[root@hayes-01 ~]# echo $?
5



# rhel9.2 scratch build
[root@hayes-02 ~]# lvcreate --yes --type vdo -n vdo_lv  -L 10G vdo_sanity -V 4503599627371008b
  Maximal supported VDO virtual size is 4.00 PiB.
[root@hayes-02 ~]# echo $?
0


Version-Release number of selected component (if applicable):
kernel-5.14.0-176.el9    BUILT: Wed Oct 12 03:57:18 AM CDT 2022
lvm2-2.03.17-0.1.20221014git04097d9.el9.test    BUILT: Fri Oct 14 01:40:16 PM CDT 2022
lvm2-libs-2.03.17-0.1.20221014git04097d9.el9.test    BUILT: Fri Oct 14 01:40:16 PM CDT 2022
Comment 1 Andy Walsh 2022-11-03 22:04:41 UTC 
(In reply to Corey Marthaler from comment #0)
>   VDO logical size is by 5120KiB bigger then limit 4096TiB.

Can we update this messaging as well?

Should read like one of these suggestions:

1. VDO logical size is 5120KiB bigger than limit of 4096TiB.
2. VDO logical size is larger than limit 4096TiB by 5120KiB.
Comment 2 Zdenek Kabelac 2022-11-08 11:45:22 UTC 
Error code return was bad - should be 5.

Fixed with this commit:

https://listman.redhat.com/archives/lvm-devel/2022-November/024464.html



Also rephrased the validation message with this commit:

https://listman.redhat.com/archives/lvm-devel/2022-November/024465.html


But in this particular case since we are now correctly 'capturing' the input error on early phase of lvcreate - we are no longer printing the message from VDO validation part -  so the message will be different as shows in the BZ description.

But error code return has to be 5.
Comment 9 Corey Marthaler 2022-12-19 21:05:54 UTC 
Verified in the latest rpms as well.

kernel-5.14.0-205.el9    BUILT: Fri Dec  2 07:14:37 AM CST 2022
lvm2-2.03.17-3.el9    BUILT: Wed Dec  7 10:41:40 AM CST 2022
lvm2-libs-2.03.17-3.el9    BUILT: Wed Dec  7 10:41:40 AM CST 2022
Comment 11 errata-xmlrpc 2023-05-09 08:23:45 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-2023:2544