Bug 1802329

Summary:	VDO reports bio statistics that are always zero.
Product:	Red Hat Enterprise Linux 8	Reporter:	Matthew Sakai <msakai>
Component:	kmod-kvdo	Assignee:	Matthew Sakai <msakai>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	awalsh, fsuba
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	6.2.3.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 02:01:16 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 2020-02-12 22:37:55 UTC

Description of problem:
VDO reports two statistics, "KVDO module bios used" and "KVO module peak bio count" which are always zero because the underlying thing they used to count doesn't exist any more. These statistics should be removed.

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

How reproducible:
100%

Steps to Reproduce:
1. Start a VDO volume
2. Get statistics using vdostats.


Actual results:
"KVDO module bios used" and "KVO module peak bio count" are reported.

Expected results:
"KVDO module bios used" and "KVO module peak bio count" are not reported.

Additional info:

Comment 3 Filip Suba 2020-07-22 08:57:15 UTC

Verified with vdo-6.2.3.107-14.el8.

# vdostats --verbose | grep KVDO
KVDO module bytes used              : 408447688
KVDO module peak bytes used         : 411659464

Comment 6 errata-xmlrpc 2020-11-04 02:01:16 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-2020:4551