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.
Description of problem:
vdo manpage allows maximum of 100 physical threads. Both vdo --help and actual results when trying to create vdo with more threads than 16 forbit values larger than 16.
Version-Release number of selected component (if applicable):
vdo-6.1.0.34-8
How reproducible:
100%
Steps to Reproduce:
1. man vdo
2. vdo --help
3. vdo create --device DEVICE --name NAME --vdoPhysicalThreads 100
Actual results:
manpage:
--vdoPhysicalThreads=thread count
Specifies the number of threads across which to subdivide parts of the VDO processing based on physical block addresses. Each additional thread after the first will use an additional 10 MB of
RAM. The default is 1; the value must be at least 0 and less than or equal to 100. vdoPhysicalThreads, vdoHashZonesThreads and vdoLogicalThreads must be either all zero or all non-zero.
help:
--vdoPhysicalThreads=<threadCount>
Specifies the number of threads across which to
subdivide parts of the VDO processing based on
physical block addresses. The default is 1; the value
must be at least 0 and less than or equal to 16.
vdoPhysicalThreads, vdoHashZonesThreads and
vdoLogicalThreads must be either all zero or all non-
zero.
vdo create command:
vdo: error: option --vdoPhysicalThreads: must be an integer at least 0 and less than or equal to 16
Expected results:
Fixed VDO manpage
Additional info:
Tested with vdo-6.1.0.46-9, manpage:
--vdoPhysicalThreads=thread count
Specifies the number of threads across which to subdivide parts of the VDO processing
based on physical block addresses. Each additional thread after the first will use an
additional 10 MB of RAM. The default is 1; the value must be at least 0 and less than or
equal to 16. vdoPhysicalThreads, vdoHashZonesThreads and vdoLogicalThreads must be
either all zero or all non-zero.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:0871
Description of problem: vdo manpage allows maximum of 100 physical threads. Both vdo --help and actual results when trying to create vdo with more threads than 16 forbit values larger than 16. Version-Release number of selected component (if applicable): vdo-6.1.0.34-8 How reproducible: 100% Steps to Reproduce: 1. man vdo 2. vdo --help 3. vdo create --device DEVICE --name NAME --vdoPhysicalThreads 100 Actual results: manpage: --vdoPhysicalThreads=thread count Specifies the number of threads across which to subdivide parts of the VDO processing based on physical block addresses. Each additional thread after the first will use an additional 10 MB of RAM. The default is 1; the value must be at least 0 and less than or equal to 100. vdoPhysicalThreads, vdoHashZonesThreads and vdoLogicalThreads must be either all zero or all non-zero. help: --vdoPhysicalThreads=<threadCount> Specifies the number of threads across which to subdivide parts of the VDO processing based on physical block addresses. The default is 1; the value must be at least 0 and less than or equal to 16. vdoPhysicalThreads, vdoHashZonesThreads and vdoLogicalThreads must be either all zero or all non- zero. vdo create command: vdo: error: option --vdoPhysicalThreads: must be an integer at least 0 and less than or equal to 16 Expected results: Fixed VDO manpage Additional info: