Bug 1928284

Summary:	There needs to be a tool to convert a VDO volume to LVMVDO
Product:	Red Hat Enterprise Linux 8	Reporter:	Andy Walsh <awalsh>
Component:	kmod-kvdo	Assignee:	Andy Walsh <awalsh>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	awalsh, cwei, emcnabb, fsuba, slegendr
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kmod-kvdo-6.2.5.41-78.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 19:28:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	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-6.2.5.65-79.el8.

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.

https://access.redhat.com/errata/RHBA-2021:4359