Bug 2058464

Summary: Suspend /resume of VDO volume may destroy deduplication index
Product: Red Hat Enterprise Linux 9 Reporter: Matthew Sakai <msakai>
Component: kmod-kvdoAssignee: Matthew Sakai <msakai>
Status: CLOSED ERRATA QA Contact: Filip Suba <fsuba>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: awalsh, cwei, fsuba, pvlasin
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kmod-kvdo-8.1.1.371-15.el9_0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2060809 (view as bug list) Environment:
Last Closed: 2022-05-17 15:49:47 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 2060809    

Description Matthew Sakai 2022-02-25 04:06:45 UTC 
Description of problem:

In some cases, suspending and resuming a VDO volume may destroy the deduplication index.

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


How reproducible:

100%

Steps to Reproduce:
1. Create a new VDO volume.
2. Write 256 blocks of known data (256 blocks == 1 megabyte)
3. Suspend the VDO device, then resume it.
4. Write the same 256 blocks to a different location on the volume.
5. Check the sttistics for the VDO device.

Actual results:

Data blocks used = 512, dedupe advice valid = 0

Expected results:

data blocks used = 256, dedupe advice valid = 256

Additional info:

This only happens if the VDO device is not stopped between the time it is created and the time it is suspended. The data written is all still accessible; only the deduplication property is lost.
Comment 6 Filip Suba 2022-03-16 09:04:04 UTC 
Verified with kmod-kvdo-8.1.1.371-15.el9_0.
Comment 8 errata-xmlrpc 2022-05-17 15:49:47 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 (new packages: kmod-kvdo), 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-2022:3919