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:
The current description of logical threads is not accurately describing the implementation.
Work is based on logical address, not hash.
Version-Release number of selected component (if applicable):
6.2.2.117
How reproducible:
100%
Actual results:
VDO Man page:
processing based on the hash value computed from the block data. The value
must be at least \*[logicalThreadsMin] and less than or equal to
\*[logicalThreadsMax]. A logical thread count of
\*[logicalThreadsBlockMapCacheSizeThreshold] or more will require explicitly
specifying a sufficiently large block map cache size, as well.
vdo --help output:
VDO processing based on the hash value computed from the block data.
The value must be at least {min} and less than or equal to {max}. A
logical thread count of {threshold} or more will require explicitly
specifying a sufficiently large block map cache size, as well.
Expected results:
VDO Man page:
processing based on the logical address. The value must be at least
\*[logicalThreadsMin] and less than or equal to \*[logicalThreadsMax].
A logical thread count of \*[logicalThreadsBlockMapCacheSizeThreshold] or
more will require explicitly specifying a sufficiently large block map cache
size.
vdo --help output:
VDO processing based on the logical address. The value must be at least
{min} and less than or equal to {max}. A logical thread count of
{threshold} or more will require explicitly specifying a sufficiently
large block map cache size.
Additional info:
Verified with vdo-6.2.3.114-14.el8.
--vdoLogicalThreads <threadCount>
Specifies the number of threads across which to
subdivide parts of the VDO processing based on the
logical address. The value must be at least 0 and less
than or equal to 60.
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 (kmod-kvdo bug fix and enhancement update), 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/RHBA-2020:4551
Description of problem: The current description of logical threads is not accurately describing the implementation. Work is based on logical address, not hash. Version-Release number of selected component (if applicable): 6.2.2.117 How reproducible: 100% Actual results: VDO Man page: processing based on the hash value computed from the block data. The value must be at least \*[logicalThreadsMin] and less than or equal to \*[logicalThreadsMax]. A logical thread count of \*[logicalThreadsBlockMapCacheSizeThreshold] or more will require explicitly specifying a sufficiently large block map cache size, as well. vdo --help output: VDO processing based on the hash value computed from the block data. The value must be at least {min} and less than or equal to {max}. A logical thread count of {threshold} or more will require explicitly specifying a sufficiently large block map cache size, as well. Expected results: VDO Man page: processing based on the logical address. The value must be at least \*[logicalThreadsMin] and less than or equal to \*[logicalThreadsMax]. A logical thread count of \*[logicalThreadsBlockMapCacheSizeThreshold] or more will require explicitly specifying a sufficiently large block map cache size. vdo --help output: VDO processing based on the logical address. The value must be at least {min} and less than or equal to {max}. A logical thread count of {threshold} or more will require explicitly specifying a sufficiently large block map cache size. Additional info: