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.
Describe the issue:
Changes to the vdo management command (vdo) include modifications of the following command options:
--albireoSparse has been renamed and changed from a pure boolean option to one requiring one of two choices.
The option is now implemented as: --sparseIndex=<disabled | enabled>; default = disabled
--sparseIndex=enabled is the logical equivalent of the previous specification of --albireoSparse.
If not specified the value for --sparseIndex is taken to be 'disabled'.
--enable512e has been renamed and changed from a pure boolean option to one requiring one of two choices.
The option is now implemented as: --emulate512=<disabled | enabled>; default = disabled
--emulate512=enabled is the logical equivalent of the previous specification of --enable512e.
If not specified the value for --emulate512 is taken to be 'disabled'.
--initializeBlockMap has changed from a pure boolean option to one requiring one of two choices.
The option is now implemented as: --initializeBlockMap=<disabled | enabled>; default = disabled
--initializeBlockMap=enabled is the logical equivalent of the previous specification of --initializeBlockMap.
If not specified the value for --initializeBlockMap is taken to be 'disabled'.
--noEnable has been renamed and changed from a pure boolean option to one requiring one of two choices.
The option is now implemented as: --activate=<disabled | enabled>; default = enabled
--activate=disabled is the logical equivalent of the previous specification of --noEnable.
If not specified the value for --activate is taken to be 'enabled'.
--vdoReadCache has been renamed to --readCache.
No other modifications have been made to it.
--vdoReadCacheSize has been renamed to --readCacheSize.
No other modifications have been made to it.
As described in Bugzilla #1494639 --initializeBlockMap has been removed as an option for the vdo management command (vdo). The changes described in this issue are no longer applicable.
I added a comment in BZ 1508920 concerning my mistake in confusing the 'vdostats --verbose' description with the output of 'vdo status'.
With that addressed, everything looks fine.