Bug 1975546 - Converted LVM VDO may suffer index loss if saved at the wrong time.
Summary: Converted LVM VDO may suffer index loss if saved at the wrong time.
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-06-23 21:42 UTC by Matthew Sakai
Modified: 2021-11-10 06:40 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:45 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:48 UTC

Description Matthew Sakai 2021-06-23 21:42:01 UTC
Description of problem:

Index state is not saved correctly during certain period after converting a managed VDO to an LVM VDO.

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

How reproducible: 100%

Steps to Reproduce:
1. Create a new VDO with vdo script and write 150G of unique data (set A) to it.
2. Close the VDO, convert it to an LVM VDO.
3. Write 150G more unique data (set B) to the VDO.
4. Close the VDO and reopen it.
5. Write set B to the VDO again.

Actual results:

Shortly into the final write, VDO should log an assertion failure about virtual chapter numbers, followed by the VDO recreating the index. Most or all of the last write will not deduplicate.

Expected results:

No error is logged. set B data deduplicates completely.

Additional info:

Comment 4 Filip Suba 2021-08-02 06:43:51 UTC
Verified with kmod-kvdo-

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