Bug 1965516 - Converted LVM VDO with sparse index loses dedupe advice.
Summary: Converted LVM VDO with sparse index loses dedupe advice.
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: 8.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: ---
Assignee: Matthew Sakai
QA Contact: Filip Suba
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-27 20:32 UTC by Matthew Sakai
Modified: 2021-11-10 06:38 UTC (History)
3 users (show)

Fixed In Version:
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

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.


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