RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1760741 - Latest kmod-kvdo does not work with latest RHEL-8.1.0 kernel [rhel-8.1.0.z]
Summary: Latest kmod-kvdo does not work with latest RHEL-8.1.0 kernel [rhel-8.1.0.z]
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: vdo-internal
QA Contact: vdo-qe
URL:
Whiteboard:
Depends On: 1695330
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-11 08:43 UTC by Oneata Mircea Teodor
Modified: 2021-09-06 15:19 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1695330
Environment:
Last Closed: 2019-10-28 17:16:42 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-28239 0 None None None 2021-09-03 15:20:06 UTC

Comment 1 Ronald Monthero 2019-10-15 06:46:23 UTC 
I encountered this issue of kvdo kernel module unable to load. 
The issue cropped up soon after a vdo install during attempt to create a vdo device as outlined below. 

kernel:  4.18.0-128.el8.x86_64
kvdo version:  kmod-kvdo-6.2.1.138-57.el8.x86_64
vdo:  vdo-6.2.1.134-11.el8.x86_64


[root@vm37-119 results]# lsblk
NAME                    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                       8:0    0    4G  0 disk 
sdb                       8:16   0    2G  0 disk               
sdc                       8:32   0    1G  0 disk 
sr0                      11:0    1 1024M  0 rom  
vda                     252:0    0   64G  0 disk 
├─vda1                  252:1    0    1G  0 part /boot
└─vda2                  252:2    0   63G  0 part 
  ├─rhel_vm37--119-root 253:0    0 39.7G  0 lvm  /
  ├─rhel_vm37--119-swap 253:1    0    4G  0 lvm  [SWAP]
  └─rhel_vm37--119-home 253:2    0 19.4G  0 lvm  /home
[root@vm37-119 results]# 

[root@vm37-119 results]# vdo create --name=vdo1-dev --device=/dev/sdb --vdoLogicalSize=120G --writePolicy=async
Creating VDO vdo1-dev
vdo: ERROR - Kernel module kvdo not installed                                     <<   kvdo  Error            
vdo: ERROR - modprobe: ERROR: could not insert 'kvdo': Exec format error  
[root@vm37-119 results]# 

== dmesg: shows messages from uds- Universal Deduplication Service -  kernel module 

[3471901.203848] uds: disagrees about version of symbol module_layout               << uds module warning soon after 
[3471974.774665] uds: disagrees about version of symbol module_layout

[root@vm37-119 results]# uname -r 
4.18.0-128.el8.x86_64+debug


modprove -v isn't very helpful either with verbose level

[root@vm37-119 results]# modprobe -v kvdo 
insmod /lib/modules/4.18.0-128.el8.x86_64+debug/weak-updates/kmod-kvdo/uds/uds.ko 
modprobe: ERROR: could not insert 'kvdo': Exec format error


modinfo for kvdo : 

[root@vm37-119 results]# modinfo kvdo
filename:       /lib/modules/4.18.0-128.el8.x86_64+debug/weak-updates/kmod-kvdo/vdo/kvdo.ko
version:        6.2.1.138
license:        GPL
author:         Red Hat, Inc.
description:    device-mapper target for transparent deduplication
rhelversion:    8.1
srcversion:     8F09BA4546AC549C462BC7A
depends:        uds,dm-mod
name:           kvdo
vermagic:       4.18.0-144.el8.x86_64 SMP mod_unload modversions 
sig_id:         PKCS#7
signer:         Red Hat Enterprise Linux Driver Update Program (key 3)
sig_key:        DF:05:CC:0A:A1:21:9E:3E
sig_hashalgo:   sha256
signature:      94:FC:64:83:FE:50:B4:65:FB:8E:25:E8:9C:28:B6:91:8F:0C:FF:8E:
		65:21:1D:CE:08:CA:E4:B4:9C:B7:C4:F4:E9:0E:DB:4F:DE:05:EE:67:
		31:84:74:FE:D0:20:5D:03:82:9A:9D:7A:41:9C:57:70:78:E6:93:B5:
		3F:AA:03:0D:45:36:60:82:A7:BB:CC:A3:E3:79:B4:F6:26:76:C4:41:
		4A:7A:45:C0:0A:3B:63:9F:00:31:04:78:3D:61:48:BC:9A:9A:AF:8B:
		EC:BB:76:8D:79:DA:79:50:88:C6:40:4A:99:AD:3F:35:48:29:F9:1E:
		5A:78:BA:55:98:91:8A:35:6F:FE:B2:E4:27:96:09:3F:80:D6:ED:12:
		37:19:74:5B:73:67:D7:59:E9:2E:B3:DB:72:04:E2:22:E1:A9:64:E7:
		DD:BC:F1:ED:A4:F6:AF:37:C6:8D:9C:7A:4E:0B:97:D6:4B:C4:05:F1:
		43:E4:A0:63:51:43:E2:D5:23:01:C1:F8:6E:B3:88:6B:FF:8C:6A:A3:
		D6:27:1F:14:EA:B9:1A:6C:A5:8D:6E:6B:31:45:ED:EA:94:4D:A8:EA:
		72:8A:3B:D2:7A:C0:45:0A:AB:3C:C6:E0:1E:4C:97:A0:52:EA:E7:46:
		9B:0A:D8:CC:8B:52:E2:80:02:FD:D4:49:35:87:66:33:08:F6:0B:E6:
		66:72:E3:6A:3B:CB:C3:D8:C3:75:8E:60:C5:50:CA:F0:79:D8:27:4C:
		7A:93:C9:83:95:C8:B2:5F:72:8A:EA:72:BB:47:55:91:B9:63:14:34:
		72:D3:56:FA:19:59:AD:42:E2:D0:EB:ED:4A:AD:2C:85:1D:83:AC:AE:
		55:9F:C8:16:9B:D3:3D:6B:53:EF:DB:9C:5B:6E:3E:8B:FD:31:62:E3:
		92:08:FA:0D:14:D2:F1:D5:0A:D2:1D:02:76:2D:A4:22:30:B3:B8:40:
		05:1D:97:CC:8F:E9:F8:DF:32:65:4C:14:3C:3F:13:DD:6F:08:32:00:
		E2:7C:1E:7E
Comment 4 Andy Walsh 2019-10-28 17:16:42 UTC 
Closing, as this was not needed for the 0-day.
Comment 5 Andy Walsh 2019-10-28 17:21:48 UTC 
(In reply to Ronald Monthero from comment #1)
I think the bug you're seeing here should be tied to 1532392 instead of this BZ.
Note You need to log in before you can comment on or make changes to this bug.