View Issue Details

IDProjectCategoryView StatusLast Update
0017799CentOS-8nfs-utilspublic2020-10-14 12:24
Reportercosmike2828 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version8.2.2004 
Target VersionFixed in Version 
Summary0017799: systemd[1]: nfs-server.service: Control process exited, code=exited status=1 --> (VDO-Volume is not READY)
Descriptionexportfs[1992]: exportfs: Failed to stat /home/datastores: No such file or directory
Oct 11 13:08:26 systemd[1]: nfs-server.service: Control process exited, code=exited status=1
Oct 11 13:08:26 systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Oct 11 13:08:26 systemd[1]: Stopped NFS server and services.

Problem is here ..that NFS-Server tries to mount (via exportfs) a VDO Volume, but VDO is not yet ready at this moment, so NFS-Server will crash
Steps To Reproduceevery time when server boots
Additional InformationOct 11 13:08:25 kernel: kvdo2:dmsetup: starting device 'vdo_home'
Oct 11 13:08:26 systemd[1]: Started Cockpit motd updater service.
Oct 11 13:08:26 exportfs[1992]: exportfs: Failed to stat /home/datastores: No such file or directory
Oct 11 13:08:26 systemd[1]: nfs-server.service: Control process exited, code=exited status=1
Oct 11 13:08:26 systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Oct 11 13:08:26 systemd[1]: Stopped NFS server and services.
Oct 11 13:08:26 systemd[1]: Starting Notify NFS peers of a restart...
Oct 11 13:08:26 systemd[1]: Stopping NFS Mount Daemon...
Oct 11 13:08:26 systemd[1]: Stopping NFSv4 ID-name mapping service...
Oct 11 13:08:26 rpc.mountd[1991]: Caught signal 15, un-registering and exiting.
Oct 11 13:08:26 systemd[1]: Stopped NFSv4 ID-name mapping service.
Oct 11 13:08:26 systemd[1]: Stopped NFS Mount Daemon.
Oct 11 13:08:26 sm-notify[2108]: Version 2.3.3 starting
Oct 11 13:08:26 systemd[1]: Started Notify NFS peers of a restart.
Oct 11 13:08:26 pmcd[1944]: Starting pmcd ...
Oct 11 13:08:26 systemd[1]: Started Performance Metrics Collector Daemon.
Oct 11 13:08:26 systemd[1]: Starting Performance Metrics Archive Logger...
Oct 11 13:08:26 swis7srv pmlogger[2131]: Starting pmlogger ...
Oct 11 13:08:26 systemd[1]: pmlogger.service: Can't open PID file /run/pcp/pmlogger.pid (yet?) after start: No such file or directory
Oct 11 13:08:26 kernel: kvdo2:journalQ: VDO commencing normal operation
Oct 11 13:08:26 kernel: kvdo2:dmsetup: Setting UDS index target state to online
Oct 11 13:08:26 kernel: uds: kvdo2:dedupeQ: loading or rebuilding index: dev=/dev/disk/by-id/dm-uuid-LVM-MViHtpSlUw0rgdja0GbworZaOuSfogjniM64LaONXiYudTSZYpQaBHxffc49WQZa offset=4096 size=2781704192
Oct 11 13:08:26 kernel: kvdo2:dmsetup: device 'vdo_home' started
Oct 11 13:08:26 kernel: kvdo2:dmsetup: resuming device 'vdo_home'
Oct 11 13:08:26 kernel: kvdo2:dmsetup: device 'vdo_home' resumed
Oct 11 13:08:26 kernel: kvdo2:packerQ: compression is enabled
Oct 11 13:08:26 systemd[1]: Found device /dev/disk/by-uuid/6f91b8cb-0b60-4aae-be6b-1020c1c754d5.
Oct 11 13:08:26 UDS/vdodmeventd[2323]: INFO (vdodmeventd/2323) VDO device vdo_home is now registered with dmeventd for monitoring
Oct 11 13:08:26 lvm[1381]: Monitoring VDO pool vdo_home.
Oct 11 13:08:26 vdo[1583]: Starting VDO vdo_data_hdd
Oct 11 13:08:26 vdo[1583]: Starting compression on VDO vdo_data_hdd
Oct 11 13:08:26 vdo[1583]: VDO instance 0 volume is ready at /dev/mapper/vdo_data_hdd
Oct 11 13:08:26 vdo[1583]: Starting VDO vdo_data_ssd
Oct 11 13:08:26 vdo[1583]: Starting compression on VDO vdo_data_ssd
Oct 11 13:08:26 vdo[1583]: VDO instance 1 volume is ready at /dev/mapper/vdo_data_ssd
Oct 11 13:08:26 vdo[1583]: Starting VDO vdo_home
Oct 11 13:08:26 vdo[1583]: Starting compression on VDO vdo_home
Oct 11 13:08:26 vdo[1583]: VDO instance 2 volume is ready at /dev/mapper/vdo_home
Oct 11 13:08:26 systemd[1]: Started VDO volume services.
Oct 11 13:08:26 systemd[1]: Mounting /home...
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2020-10-14 09:57 cosmike2828 New Issue