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:
There is missing information in manpage about link between block map cache size and logical thread count. The default 128MB block map cache can support up to 8 logical threads (try-error), so to have more logical threads, user also has to increase block map cache size. I assume this could be done automatically, increasing default block map cache size if it is not large enough. But never the less this information should be in manpage.


Version-Release number of selected component (if applicable):
vdo-6.1.0.34-8

How reproducible:
100%

Steps to Reproduce:
1. vdo create --device DEVICE --name NAME --vdoLogicalThreads 100

Actual results:
vdo: ERROR - Insufficient block map cache for vdo
No hint in manpage about this

Expected results:
vdo: ERROR - Insufficient block map cache for vdo / or VDO succesfully creted with larger block map cache size
Information in manpage about this link

Additional info:

The "vdo" man page does mention this under the --blockMapCacheSize option, but the doc for --vdoLogicalThreads doesn't touch on it. Easy enough to fix...

vdo-6.1.0.55-10

manpage:
--blockMapCacheSize "The cache must be at least 16MB per logical thread. Note that there is a memory overhead of 15%."
--vdoLogicalThreads "A logical thread count over 8 will require explicitly specifying a sufficiently large block map cache size, as well."

--help:
--vdoLogicalThreads "A logical thread count over 8 will require explicitly specifying a sufficiently large block map cache size, as well."

The info about logical threads is missing at --helps --blockMapCacheSize, but it is in manpage, which is enough with this specific info. There is enough info at --vdoLogicalThreads in both manpage and --help.

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