Bug 1928284 - There needs to be a tool to convert a VDO volume to LVMVDO
Summary: There needs to be a tool to convert a VDO volume to LVMVDO
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: 8.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Andy Walsh
QA Contact: Filip Suba
Depends On:
Blocks: 1930261
TreeView+ depends on / blocked
Reported: 2021-02-12 20:44 UTC by Andy Walsh
Modified: 2021-11-10 06:38 UTC (History)
5 users (show)

Fixed In Version: kmod-kvdo-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-09 19:28:28 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4359 0 None None None 2021-11-09 19:28:38 UTC

Internal Links: 1930261

Description Andy Walsh 2021-02-12 20:44:10 UTC
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.

Comment 4 Susan LeGendre-McGhee 2021-05-27 21:01:49 UTC
The code has been updated and is available in the latest version.

Comment 7 Filip Suba 2021-08-02 06:45:13 UTC
Verified with kmod-kvdo-

Comment 10 errata-xmlrpc 2021-11-09 19:28:28 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.