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 a VDO device is suspended, and a new table is loaded that points to a new backing device, after resuming the VDO will continue to write some metadata to the original device. (This especially affects metadata related to the deduplication index.) It also retains a reference to the original device, possibly preventing the original device from being removed.

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


How reproducible:


Steps to Reproduce:
1. Create a VDO, add some data, and suspend it.
2. Change the underlying device stack, for example by adding a cache or replacing the backing store with a RAID.
3. Load a new table for the VDO reflecting the new backing device, and resume the VDO.


Actual results:
The exact effect likely varies but at a minimum it may result in a loss of deduplication information.


Expected results:
Normal VDO operation

Additional info:
This issue can be worked around by stopping the VDO device completely and restarting it with the new table.

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