Bug 2079048
| Summary: | most virtual size attempts around (and including) the mentioned limit fail with "logical size is by 1024KiB bigger then limit 4096TiB" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> |
| lvm2 sub component: | VDO | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED MIGRATED | Docs Contact: | |
| Severity: | low | ||
| Priority: | unspecified | CC: | agk, awalsh, heinzm, jbrassow, mcsontos, prajnoha, zkabelac |
| Version: | 8.6 | Keywords: | MigratedToJIRA, Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-23 15:58:09 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-04-26 18:58:26 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. 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. [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 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. 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. 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. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |