Description of problem:
A VDO with a sparse index will lose all dedupe information after conversion.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a VDO with a sparse deduplication index. Add some data to it. Observe the number of data blocks used.
2. Convert the VDO to an LVM VDO (using the tool soon to be published)
3. Write the same data to a new region of the VDO volume.
"Data blocks used" count doubles after second write.
"Data blocks used" does not change after second write.
Verified with kmod-kvdo-188.8.131.52-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.