Bug 1966824

Summary:	Converted LVM VDO sometimes won't rebuild properly after a crash
Product:	Red Hat Enterprise Linux 8	Reporter:	Matthew Sakai <msakai>
Component:	kmod-kvdo	Assignee:	John Wiele <jwiele>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.5	CC:	awalsh, cwei, fsuba, jwiele
Target Milestone:	beta	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	6.2.5.64	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 19:28:45 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:

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.

2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Filip Suba 2021-07-30 13:00:11 UTC

Verified with kmod-kvdo-6.2.5.65-79.el8.

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.

https://access.redhat.com/errata/RHBA-2021:4359