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:
If the user creates a VDO volume with --indexMem=10, it will create a VDO volume with a UDS index in dense mode that uses 10 GB of memory, and attempts to reserve 100 GB of storage space on the configured device.  This would call the 

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

How reproducible:
100%

Steps to Reproduce:
1. Install the kmod-kvdo and vdo packages.
2. Add a storage device that has less than the required amount of disk space for a UDS index.
3. Execute "vdo create --name=vdo1 --device=<device> --indexMem=10 --verbose (or use an "--indexMem=" value corresponding to about 1 GB of memory per 10 GB of storage space, in a way that yields insufficient storage space to contain the index).

Actual results:
vdo: ERROR - vdoformat: formatVDO failed on '/dev/sdc': VDO Status: Exceeds maximum number of slabs supported

Expected results:
vdoformat prints a message indicating that there is not enough space to create the UDS index.

Additional info:

In a case where the device has enough space to create the index, but does not have enough space to create a full slab (default size 2 GB), this error will appear:

vdo: ERROR - vdoformat: formatVDO failed on '/dev/TEST/backing': VDO Status: Out of space

The test logical volume above was 4 GB in size; it was enough to contain the 2.5 GB UDS index, but not enough to contain a single 2 GB slab.

*** Bug 1505748 has been marked as a duplicate of this bug. ***

vdo-6.1.0.55-10 with 5.5T disk:

# vdo create --name vdo2 --device /dev/sdg --indexMem 1000 --verbose
Creating VDO vdo2
    modprobe kvdo
    vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=1000 /dev/sdg
vdo: ERROR - vdoformat: formatVDO failed on '/dev/sdg': VDO Status: Out of space

THe new indication does not specifically says there is not enough space for the index, but it clearly says it is a space issue, which is good enough.

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