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.
Bug 1520991 - vdo create --indexMem > 1024 gives wrong error
Summary: vdo create --indexMem > 1024 gives wrong error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: vdo
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: bjohnsto
QA Contact: Jakub Krysl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-05 15:20 UTC by Jakub Krysl
Modified: 2019-03-06 02:16 UTC (History)
6 users (show)

Fixed In Version: 6.1.0.97
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 15:48:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0871 0 None None None 2018-04-10 15:49:01 UTC

Description Jakub Krysl 2017-12-05 15:20:40 UTC 
Description of problem:

This is correct:
# vdo create --name vdo --device /dev/sdc --verbose --indexMem 1024
Creating VDO vdo
    pvcreate -qq --test /dev/sdc
    modprobe kvdo
    vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=1024 /dev/sdc
vdo: ERROR - vdoformat: formatVDO failed on '/dev/sdc': VDO Status: Out of space

This fails with wrong error:
# vdo create --name vdo --device /dev/sdc --verbose --indexMem 1025
Creating VDO vdo
    pvcreate -qq --test /dev/sdc
    modprobe kvdo
    vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=102500 /dev/sdc
vdo: ERROR - vdoformat: formatVDO failed on '/dev/sdc': UDS Error: Configured memory too small or unsupported size

It appears VDO does not check for indexMem value > 1024 and instead tries to create the index. But it fails creating at all leading to the index being too small (e.g. 0 I guess).

Version-Release number of selected component (if applicable):
vdo-6.1.0.72-12

How reproducible:
100%

Steps to Reproduce:
1. vdo create --name vdo --device device --indexMem 1025


Actual results:
vdo: ERROR - vdoformat: formatVDO failed on '/dev/sdc': UDS Error: Configured memory too small or unsupported size

Expected results:
vdo: error: option --indexMem: must be index memory value and less than 1025

Additional info:
Comment 3 Jakub Krysl 2017-12-14 11:16:25 UTC 
Wrong values now give correct errors:

# vdo create --name vdo --device /dev/sdc --indexMem 1024 --force
Creating VDO vdo
vdo: ERROR - Not enough available memory in system for index requirement of 1T

# vdo create --name vdo --device /dev/sdc --indexMem 1025
usage: vdo create [-h] -n <volume> --device <devicepath>
                  [--activate {disabled,enabled}]
                  [--blockMapCacheSize <megabytes>]
                  [--blockMapPeriod <period>]
                  [--compression {disabled,enabled}]
                  [--deduplication {disabled,enabled}]
                  [--emulate512 {disabled,enabled}] [--force]
                  [--indexMem <gigabytes>] [--readCache {disabled,enabled}]
                  [--readCacheSize <megabytes>]
                  [--sparseIndex {disabled,enabled}]
                  [--vdoAckThreads <threadCount>]
                  [--vdoBioRotationInterval <ioCount>]
                  [--vdoBioThreads <threadCount>]
                  [--vdoCpuThreads <threadCount>]
                  [--vdoHashZoneThreads <threadCount>]
                  [--vdoLogicalSize <megabytes>]
                  [--vdoLogicalThreads <threadCount>]
                  [--vdoLogLevel {critical,error,warning,notice,info,debug}]
                  [--vdoPhysicalThreads <threadCount>]
                  [--vdoSlabSize <megabytes>] [--writePolicy {async,sync}]
                  [-f <file>] [--logfile <pathname>] [--verbose]
vdo create: error: argument --indexMem: must be an integer at least 1 and less than or equal to 1024 or one of the special values of 0.25, 0.5, or 0.75
Comment 6 errata-xmlrpc 2018-04-10 15:48:32 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.