Hide Forgot
Description of problem: With the new introduction of the LVMVDO implementation, users need the ability to convert from a VDO Manager based VDO volume to an LVMVDO based VDO volume. Expected behavior: Create a VDO volume. (and write some data) Stop the VDO volume. Run the utility or utilities) on the backing device. Start the LVMVDO volume and verify data is intact and deduplication is still achieved against that data.
The code has been updated and is available in the latest version.
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