Bug 1965516

Summary: Converted LVM VDO with sparse index loses dedupe advice.
Product: Red Hat Enterprise Linux 8 Reporter: Matthew Sakai <msakai>
Component: kmod-kvdoAssignee: Matthew Sakai <msakai>
Status: CLOSED ERRATA QA Contact: Filip Suba <fsuba>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.5CC: awalsh, cwei, fsuba
Target Milestone: betaKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: 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:

Description Matthew Sakai 2021-05-27 20:32:28 UTC
Description of problem:

A VDO with a sparse index will lose all dedupe information after conversion.

Version-Release number of selected component (if applicable):

How reproducible:


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.

Actual results:

"Data blocks used" count doubles after second write.

Expected results:

"Data blocks used" does not change after second write.

Additional info:

Comment 4 Filip Suba 2021-08-02 06:42:59 UTC
Verified with kmod-kvdo-

Comment 7 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.