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.
lvm2 code added esitamation for memory requirements needed by running VDO target.
This function however incorrectly estimates the size when VDO volume is resized and could even potentially leave device in suspended state since the calculation were provided also during already suspended state.
Also provided guiding messages were misleading user about required memory.
Bug is present in released upstream version 2.03.18
and is fixed with these commits (in upstream 2.03.19):
https://listman.redhat.com/archives/lvm-devel/2023-January/024531.htmlhttps://listman.redhat.com/archives/lvm-devel/2023-January/024532.htmlhttps://listman.redhat.com/archives/lvm-devel/2023-January/024533.htmlhttps://listman.redhat.com/archives/lvm-devel/2023-January/024534.htmlhttps://listman.redhat.com/archives/lvm-devel/2023-January/024534.html
To test correct behavior -
Find some largest support virtual size VDO LV for VDO-Pool LV on given hardware - i.e. for 4GiB RAM system check if i.e. 1.5PiB VDO LV can be created. Remove such VDO LV, and create new one with 1PiB virtual VDO volume size and try to extend this virtual VDO volume by i.e. 500TiB - with fixed version this should work - previously lvm2 command has failed.
This bug is mainly show when exercising very large sizes of virtual VDO volumes and was not noticed within ~TiB range volume sizes used in common testing.
Also patches now correctly handles input sizes about allowed range where lvm2 errored command with incorrect/misleading error message (i.e. check 'lvcreate -L4P)
Comment 4RHEL Program Management
2023-09-23 18:37:15 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 5RHEL Program Management
2023-09-23 18:39:33 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.