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:
When running command with physical thread count > slab count, user gets following errors:
# vdo create --name='vdo_test' --vdoPhysicalThreads='5' --device='/dev/sdc' --vdoHashZoneThreads='5' --vdoLogicalThreads='5' --vdoSlabSize='2G'
Creating VDO vdo_test
Starting VDO vdo_test
Removing VDO vdo_test
Stopping VDO vdo_test
vdo: ERROR - Could not set up device mapper for vdo_test
vdo: ERROR - device-mapper: reload ioctl on vdo_test failed: Input/output error
/var/log/messages:
[ 379.753922] kvdo23:dmsetup: starting device 'vdo_test'
[ 379.781003] kvdo23:dmsetup: underlying device, REQ_FLUSH: not supported, REQ_FUA: not supported
[ 379.824011] kvdo23:dmsetup: Using write policy sync automatically.
[ 379.851695] kvdo23:dmsetup: zones: 5 logical, 5 physical, 5 hash; base threads: 17
[ 379.894409] kvdo23:journalQ: 5 physical zones exceeds slab count 3: kvdo: Bad configuration option (2053)
[ 379.937494] kvdo23:journalQ: aborting load: kvdo: Bad configuration option (2053)
[ 379.971333] kvdo23:dmsetup: Could not start kernel physical layer. (VDO error 2053, message Cannot load metadata from device)
[ 380.025339] kvdo23:dmsetup: mapToSystemError: mapping internal status code 2053 (kvdo: VDO_BAD_CONFIGURATION: kvdo: Bad configuration option) to EIO
[ 380.085725] device-mapper: table: 253:0: vdo: Cannot load metadata from device
[ 380.118253] device-mapper: ioctl: error adding target to table
As error propagation is subject to other BZs (for example BZ 1512134), this ticket asks for only giving this information to user via manpage, as there is no mention about this:
# man vdo
--vdoPhysicalThreads=thread count Specifies the number of threads across which to subdivide parts of the VDO processing based on physical block addresses. The value must be at least 0 and less than or equal to 16. Each additional thread after the first will use an additional 10 MB of RAM. vdoPhysicalThreads, vdoHashZonesThreads and vdoLogicalThreads must be either all zero or all non-zero. The default is 1.
Version-Release number of selected component (if applicable):
vdo-6.1.1.125-3.el7
How reproducible:
100%
Steps to Reproduce:
1. vdo create --name='vdo_test' --vdoPhysicalThreads='5' --device='/dev/sdc' --vdoHashZoneThreads='5' --vdoLogicalThreads='5' --vdoSlabSize='2G'
2. man vdo
Actual results:
No mention of requirement vdoPhysicalThreads <= vdo slab count
Expected results:
vdoPhysicalThreads <= vdo slab count documented in man page
Additional info:
Verified with vdo-6.2.2.117-13.el8.
--vdoPhysicalThreads=thread count
Specifies the number of threads across which to subdivide parts of the VDO processing based on physical block addresses. The value must be at least 0 and less than or equal to 16. The value must also be less than or equal to the slab count...
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/RHBA-2020:1782