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:

In some cases, suspending and resuming a VDO volume may destroy the deduplication index.

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


How reproducible:

100%

Steps to Reproduce:
1. Create a new VDO volume.
2. Write 256 blocks of known data (256 blocks == 1 megabyte)
3. Suspend the VDO device, then resume it.
4. Write the same 256 blocks to a different location on the volume.
5. Check the sttistics for the VDO device.

Actual results:

Data blocks used = 512, dedupe advice valid = 0

Expected results:

data blocks used = 256, dedupe advice valid = 256

Additional info:

This only happens if the VDO device is not stopped between the time it is created and the time it is suspended. The data written is all still accessible; only the deduplication property is lost.

Verified with kmod-kvdo-8.1.1.371-15.el9_0.

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 (new packages: kmod-kvdo), 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-2022:3919