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.
vdo_slab_size_mb needs to be added to this bug as well. Also odd that the property is "vdo_slab_size_mb", yet the default is a size listed in gb.
Unrecognised field: vdo_slab_size_mb
[root@hayes-01 ~]# lvs -o vdo_slab_size vdo_sanity/vdo_lv
VDOSlabSize
2.00g
Comment 3RHEL Program Management
2023-09-23 18:21:40 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 4RHEL Program Management
2023-09-23 18:35:10 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.
Description of problem: B. index_memory_size_mb is required to set but index_memory_size to see it w/ lvs [root@hayes-01 ~]# lvconvert --yes --type vdo-pool -n vdo_lv --vdosettings 'vdo_index_memory_size=256' -V 20G vdo_sanity/vdo_pool Unknown VDO setting "vdo_index_memory_size". [root@hayes-01 ~]# lvconvert --yes --type vdo-pool -n vdo_lv --vdosettings 'vdo_index_memory_size_mb=256' -V 20G vdo_sanity/vdo_pool WARNING: Converting logical volume vdo_sanity/vdo_pool to VDO pool volume with formating. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) The VDO volume can address 2 GB in 1 data slab. 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. Logical volume "vdo_lv" created. Converted vdo_sanity/vdo_pool to VDO pool volume and created virtual vdo_sanity/vdo_lv VDO volume. [root@hayes-01 ~]# lvs -o vdo_index_memory_size_mb vdo_sanity/vdo_lv [...] Unrecognised field: vdo_index_memory_size_mb [root@hayes-01 ~]# lvs -o vdo_index_memory_size vdo_sanity/vdo_lv VDOIndexMemorySize 256.00m C. same with block_map_cache_size_mb [root@hayes-01 ~]# lvs -o vdo_block_map_cache_size_mb vdo_sanity/vdo_lv [...] Unrecognised field: vdo_block_map_cache_size_mb [root@hayes-01 ~]# lvs -o vdo_block_map_cache_size vdo_sanity/vdo_lv VDOBlockMapCacheSize 128.00m [root@hayes-01 ~]# lvchange --vdosettings 'vdo_block_map_cache_size = 256' vdo_sanity/vdo_pool Unknown VDO setting "vdo_block_map_cache_size". [root@hayes-01 ~]# lvchange --vdosettings 'vdo_block_map_cache_size_mb = 256' vdo_sanity/vdo_pool Logical volume vdo_sanity/vdo_pool changed. [root@hayes-01 ~]# lvs -o vdo_block_map_cache_size vdo_sanity/vdo_lv VDOBlockMapCacheSize 256.00m Version-Release number of selected component (if applicable): kernel-4.18.0-398.g366e.el8.kpq1 BUILT: Tue Jun 7 04:56:38 CDT 2022 lvm2-2.03.14-4.el8 BUILT: Wed Jun 15 17:14:34 CDT 2022 lvm2-libs-2.03.14-4.el8 BUILT: Wed Jun 15 17:14:34 CDT 2022 How reproducible: Everytime