Description of problem:
After converting a non-lvm VDO to an lvm VDO, the crash recovery process of the index may not work correctly. If it fails, it would result in the index being removed and a new one being created in its place, destroying all previous deduplication information. This can only happen if any pre-conversion part of the index is still valid, so if enough data is written to the converted VDO volume, it will no longer be possible to encounter this problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. I actually do not know how to reproduce this yet with a full VDO; the bug was found by inspection of the UDS index code. SanityOnly checking seems suficient.
Verified with kmod-kvdo-184.108.40.206-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.