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 doing a suspend of a VDO volume, one step is to suspend the UDS index. If the suspend does not save the entire index state, then the index may continue to write data even after it claims to be suspended. (This is the sort of suspend that can happen when growing or replacing the underlying device, for example.) This issue was detected by code inspection.

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


How reproducible:

Steps to Reproduce:
This condition is likely hard to reproduce with an ordinary VDO device, but it may be possible to create a VDO volume where the index region (the first 2GB or so) can be made artificially slow by using a dm-delay device behind it. With this kind of setup...

1. Create and start the VDO volume. Wait a while until the index is also online. 
2. Write 3-5GB of data to the VDO volume in order to make some work for the index.
3. Suspend the VDO without saving.

Actual results:
Suspend should complete fairly quickly, but I/O to the index region may continue.

Expected results:
Suspend should not complete until index I/O has completed.


Additional info:

Verified with kmod-kvdo-6.2.5.72-79.el8.

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-2021:4359