View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0017928CentOS-8kmod-kvdopublic2020-12-09 22:372020-12-18 02:19
Reportercosmike2828 Assigned To 
PriorityimmediateSeverityblockReproducibilityalways
Status resolvedResolutionfixed 
PlatformHPE DL20 Gen10OSCentOS Linux release 8.3.2011OS Version8.3.2011
Product Version8.3.2011 
Summary0017928: ERROR - modprobe: FATAL: Module kvdo not found
DescriptionChoose (start, stop, restart, try-restart, reload, force-reload, status) : status
● vdo.service - VDO volume services
   Loaded: loaded (/usr/lib/systemd/system/vdo.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-12-09 22:48:20 CET; 33min ago
  Process: 1394 ExecStart=/usr/bin/vdo start --all --confFile /etc/vdoconf.yml (code=exited, status=1/FAILURE)
 Main PID: 1394 (code=exited, status=1/FAILURE)

Dec 09 22:48:19 xxx systemd[1]: Starting VDO volume services...
Dec 09 22:48:19 xxx vdo[1394]: vdo: ERROR - Kernel module kvdo not installed
Dec 09 22:48:19 xxx vdo[1394]: ERROR - Kernel module kvdo not installed
Dec 09 22:48:19 xxx vdo[1394]: ERROR - modprobe: FATAL: Module kvdo not found in directory /lib/modules/4.18.0-240.1.1.el8_3.x86_64
Dec 09 22:48:19 xxx vdo[1394]: vdo: ERROR - modprobe: FATAL: Module kvdo not found in directory /lib/modules/4.18.0-240.1.1.el8_3.x86_64
Dec 09 22:48:19 xxx vdo[1394]: Starting VDO vdo_home
Dec 09 22:48:20 xxx systemd[1]: vdo.service: Main process exited, code=exited, status=1/FAILURE
Dec 09 22:48:20 xxx systemd[1]: vdo.service: Failed with result 'exit-code'.
Dec 09 22:48:20 xxx systemd[1]: Failed to start VDO volume services.
Steps To Reproducei did the upgrade also on HPE DL360 G7 System - the result is the same.

The Data User access is broken - this is a very important system (CLOUD).
Red Had need to take care of VDO - because of data consistency.

Kernel: 4.18.0-240.1.1.el8_3.x86_64

VDO Version:
-------------------
vdo-6.2.3.114-14.el8.x86_64
kmod-kvdo-6.2.2.117-65.el8.x86_64


Additional Informationi did restart the the System with the a previous kernel (4.18.0-193.19.1.el8_2.x86_64)
But the VDO is not working properly anymore.

[root@xxxx ~]# vdostats
VDOStatistics version mismatch
TagsVDO

Activities

cosmike2828

cosmike2828

2020-12-09 22:37

reporter  

ScreenShot1093.jpg (1,375,147 bytes)
toracat

toracat

2020-12-10 05:08

manager   ~0038058

A newer version of kmod-kvdo is required for CentOS 8.3:

kmod-kvdo-6.2.3.114-74.el8

@JohnnyHughes

Could you build/release this version?
cosmike2828

cosmike2828

2020-12-10 15:21

reporter   ~0038066

I did -->
1.) download the following RPMs from --> http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/

vdo-support-6.2.4.14-14.el8.x86_64
vdo-6.2.4.14-14.el8.x86_64
kmod-kvdo-6.2.3.91-73.el8.x86_64

2. ) did install all of them
3.) Then did a reboot with the new new 8.3 Kernel (4.18.0-240.1.1.el8_3.x86_64).

Now VDO seems to work again.
cosmike2828

cosmike2828

2020-12-10 15:28

reporter   ~0038067

I think VDO is a great achievement, a good development in the right direction.

On the other hand, Centos/Red Had should be aware that there are a lot of people who use productive data with VDO and you should consider the development as one unit - together with the OS, together with the kernel.

There are a number of operating systems where this sensitivity is implemented - like TrueNAS (tight coupling of OS + dedup + compression (with ZFS of course)). With Netapp it is clear - this is exclusively an enterprise product - but also Nutanix & CO and of course ZFS.

Thanks for your quick support - i do appreciate , Johnny !
cosmike2828

cosmike2828

2020-12-10 15:33

reporter   ~0038068

Johnny .. btw .. is there any reason why Kernel Module for VDO get forgotten ..hm .. maybe to say - in a regular manner ?
antigerme

antigerme

2020-12-16 19:28

reporter   ~0038091

Today I did a "upgrade" from centos release to centos stream and kmod-kvdo broke

kernel-4.18.0-257.el8.x86_64
kmod-kvdo-6.2.3.91-73.el8.x86_64

The kmod-kvdo-6.2.3.91-73.el8.x86_64 from centos stream repo is to kernel 4.18.0-211.el8.x86_64

[root@xkcd ~]# rpm -ql kmod-kvdo
/etc/depmod.d/kvdo.conf
/lib/modules/4.18.0-211.el8.x86_64
/lib/modules/4.18.0-211.el8.x86_64/extra
/lib/modules/4.18.0-211.el8.x86_64/extra/kmod-kvdo
/lib/modules/4.18.0-211.el8.x86_64/extra/kmod-kvdo/uds
/lib/modules/4.18.0-211.el8.x86_64/extra/kmod-kvdo/uds/uds.ko
/lib/modules/4.18.0-211.el8.x86_64/extra/kmod-kvdo/vdo
/lib/modules/4.18.0-211.el8.x86_64/extra/kmod-kvdo/vdo/kvdo.ko
cosmike2828

cosmike2828

2020-12-17 13:08

reporter   ~0038098

goot hint, thx antigerme.

so, then Kernel 4.18.0-240.1.1.el8_3.x86_64 seems to work with kmod-kvdo-6.2.3.91-73.el8.x86_64, but not with Kernel kernel-4.18.0-257.el8.x86_64.

I'm looking now how i can build kmod-kvdo-6.2.3.114-74.el8 (or probably downlaod ?) (that's what toracat proposed recently).
cosmike2828

cosmike2828

2020-12-17 13:24

reporter   ~0038099

https://git.centos.org/rpms/kmod-kvdo/releases found it there
toracat

toracat

2020-12-18 02:18

manager   ~0038107

@cosmike2828

In the future, please file a bug report related to CentOS Stream at:

https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%208&version=CentOS%20Stream

Issue History

Date Modified Username Field Change
2020-12-09 22:37 cosmike2828 New Issue
2020-12-09 22:37 cosmike2828 File Added: ScreenShot1093.jpg
2020-12-09 22:37 cosmike2828 Tag Attached: VDO
2020-12-10 05:08 toracat Note Added: 0038058
2020-12-10 05:17 toracat Status new => assigned
2020-12-10 05:17 toracat Description Updated
2020-12-10 05:17 toracat Steps to Reproduce Updated
2020-12-10 05:17 toracat Additional Information Updated
2020-12-10 15:21 cosmike2828 Note Added: 0038066
2020-12-10 15:28 cosmike2828 Note Added: 0038067
2020-12-10 15:33 cosmike2828 Note Added: 0038068
2020-12-16 19:28 antigerme Note Added: 0038091
2020-12-17 13:08 cosmike2828 Note Added: 0038098
2020-12-17 13:24 cosmike2828 Note Added: 0038099
2020-12-18 02:18 toracat Note Added: 0038107
2020-12-18 02:19 toracat Status assigned => resolved
2020-12-18 02:19 toracat Resolution open => fixed