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 2079048 - most virtual size attempts around (and including) the mentioned limit fail with "logical size is by 1024KiB bigger then limit 4096TiB"
Summary: most virtual size attempts around (and including) the mentioned limit fail wi...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.6
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-26 18:58 UTC by Corey Marthaler
Modified: 2024-01-22 04:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-23 15:58:09 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-8266 0 None Migrated None 2023-09-23 15:54:53 UTC
Red Hat Issue Tracker RHELPLAN-120031 0 None None None 2022-04-26 19:06:24 UTC

Description Corey Marthaler 2022-04-26 18:58:26 UTC 
Description of problem:
[root@hayes-01 archive]# vgs
  VG         #PV #LV #SN Attr   VSize  VFree 
  vdo_sanity   6   0   0 wz--n- 10.91t 10.91t

[root@hayes-01 archive]# lvcreate --yes --type vdo -n vdo_lv  -L 10G vdo_sanity -V 4096TiB
  VDO logical size is by 1024KiB bigger then limit 4096TiB.


A. What the error provides for the correct limit should work.

B. It's the virtual size we're dealing with, not the logical size of the pool.

C. Grammatically, "size is by 1024KiB bigger then limit" should be "size is 1024KiB bigger than limit".




[root@hayes-01 archive]# lvcreate --yes --type vdo -n vdo_lv  -L 10G vdo_sanity -V 4503599627370496b
  VDO logical size is by 1024KiB bigger then limit 4096TiB.


Version-Release number of selected component (if applicable):
kernel-4.18.0-372.5.1.el8    BUILT: Mon Mar 28 10:29:22 CDT 2022
lvm2-2.03.14-3.el8    BUILT: Tue Jan  4 14:54:16 CST 2022
lvm2-libs-2.03.14-3.el8    BUILT: Tue Jan  4 14:54:16 CST 2022
Comment 1 Corey Marthaler 2022-04-27 19:08:06 UTC 
Extensions need to be looked at as well.

[root@hayes-01 ~]# lvextend --yes -l1000000%FREE vdo_sanity/vdo_lv 
  Size of logical volume vdo_sanity/vdo_lv changed from 1.00 PiB (268435456 extents) to <11.53 PiB (3093770400 extents).
  VDO logical size is by 8274037048320KiB bigger then limit 4096TiB.
  Failed to suspend logical volume vdo_sanity/vdo_lv.
Comment 2 Zdenek Kabelac 2022-08-26 14:06:15 UTC 
Progress for this moment in upstream:

Check for free RAM:

https://listman.redhat.com/archives/lvm-devel/2022-July/024233.html

Man page updates about memory usage:

https://listman.redhat.com/archives/lvm-devel/2022-July/024230.html

Enhanced detection of size acceptance fro vdo/pool volumes:

https://listman.redhat.com/archives/lvm-devel/2022-July/024235.html

Some more surrounding patches might be needed for some new defines and parameter range checks.
Comment 3 Corey Marthaler 2022-11-02 21:41:49 UTC 
[root@hayes-02 ~]# lvextend --yes -l1000000%FREE vdo_sanity/vdo_lv 
  Unable to extend vdo_sanity/vdo_lv by 4165989536 logical extents: exceeds limit (4294967295).
[root@hayes-02 ~]# echo $?
5

Here's what's in the scratch build. Is this now what's expected? The posted "limit" (4294967295) is greater than the requested amount, yet the warning states the opposite.


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 4 Zdenek Kabelac 2023-02-03 11:23:33 UTC 
Further enhancement with:

https://listman.redhat.com/archives/lvm-devel/2023-January/024531.html
https://listman.redhat.com/archives/lvm-devel/2023-January/024532.html
https://listman.redhat.com/archives/lvm-devel/2023-January/024533.html
https://listman.redhat.com/archives/lvm-devel/2023-January/024534.html

should be giving you more user friendly messages and also correctly validate memory requirements by such configuration - i.e. for PiB size a lot of RAM is required.

The message in comment 3 though was correct - as the limit is  2^32 extents - and your requested additional extension 'size' (extend by) which has been calculated to 4165989536 would have make the total  LV volume size exceeding the maximal size of extent we can express as 32bit number - so the message was possibly harder to read and follow - with the above patch set however we should get also nicer this message with reporting volume size in human readable size format.
Comment 7 RHEL Program Management 2023-09-23 15:52:49 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 8 RHEL Program Management 2023-09-23 15:58:09 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.
Comment 9 Red Hat Bugzilla 2024-01-22 04:25:14 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.