Bug 2045885

Summary:	vdostats: fails when device-mapper devices have a different major number than 253
Product:	Red Hat Enterprise Linux 9	Reporter:	bjohnsto
Component:	kmod-kvdo	Assignee:	bjohnsto
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	awalsh, cwei
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdo-8.1.1.360-1.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		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:

Description bjohnsto 2022-01-25 20:57:05 UTC

Description of problem:

On certain machines, DM devices have a major number of 252 instead of 253. This causes vdostats to fail, as its doing a specific check.

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


How reproducible:

Depends on machine

Steps to Reproduce:
1. Look in /proc/devices. Make sure device-mapper devices are major number 252.
2. Create a VDO volume and then run vdostats

Actual results:

Observe error number about illegal major number.

Expected results:

No error.

Additional info:

Comment 5 Filip Suba 2022-02-28 12:28:35 UTC

Verified with vdo-8.1.1.360-1.el9.

Comment 7 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