Hide Forgot
Description of problem: Index state is not saved correctly during certain period after converting a managed VDO to an LVM VDO. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a new VDO with vdo script and write 150G of unique data (set A) to it. 2. Close the VDO, convert it to an LVM VDO. 3. Write 150G more unique data (set B) to the VDO. 4. Close the VDO and reopen it. 5. Write set B to the VDO again. Actual results: Shortly into the final write, VDO should log an assertion failure about virtual chapter numbers, followed by the VDO recreating the index. Most or all of the last write will not deduplicate. Expected results: No error is logged. set B data deduplicates completely. Additional info:
Verified with kmod-kvdo-6.2.5.65-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