Bug 1966824 - Converted LVM VDO sometimes won't rebuild properly after a crash
Summary: Converted LVM VDO sometimes won't rebuild properly after a crash
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: John Wiele
QA Contact: Filip Suba
Depends On:
TreeView+ depends on / blocked
Reported: 2021-06-02 00:54 UTC by Matthew Sakai
Modified: 2021-11-10 06:40 UTC (History)
4 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-02 00:54:26 UTC
Description of problem:
After converting a non-lvm VDO to an lvm VDO, the crash recovery process of the index may not work correctly. If it fails, it would result in the index being removed and a new one being created in its place, destroying all previous deduplication information. This can only happen if any pre-conversion part of the index is still valid, so if enough data is written to the converted VDO volume, it will no longer be possible to encounter this problem.

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

How reproducible:

Steps to Reproduce:
1. I actually do not know how to reproduce this yet with a full VDO; the bug was found by inspection of the UDS index code. SanityOnly checking seems suficient.


Actual results:

Expected results:

Additional info:

Comment 4 Filip Suba 2021-07-30 13:00:11 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.