Unable to start vxvm-fstab-automount.service after upgrade from VRTSVxvm 7.1.0.100 to 7.1.0.200 or 7.1.0.300

book

Article ID: 100043258

calendar_today

Updated On:

Description

Error Message

# systemctl status vxvm-fstab-automount.service
Unit vxvm-fstab-automount.service could not be found.
 

Cause

If CPI hotfix (cpi-Patch-7.1.0.900) is not applied during upgrade from VRTSvxvm 7.1.0.100 to  VRTSvxvm 7.1.0.200/300 then file /usr/lib/systemd/system/vxvm-fstab-automount.service gets removed during upgrade.

 

Resolution

If CPI hotfix (cpi-Patch-7.1.0.900) is not applied during upgrade then copy the missing file manually from /etc/vx/systemd/vxvm-fstab-automount.service to /usr/lib/systemd/system/ and enable vxvm-fstab-automount.service.

# cp -f /etc/vx/systemd/vxvm-fstab-automount.service /usr/lib/systemd/system/   

# systemctl enable vxvm-fstab-automount.service 

# systemctl --system daemon-reload 

 

Note: Please note Veritas engineering has further enhanced the integration between Veritas Storage Foundation / InfoScale with Linux systemd by utilizing the udev triggers.   As a result, vxvm-fstab-automount.service will be soon be obsolete.  Please refer to Veritas VxVM and SystemD integration for more details on the udev integration.

 

 

 

Issue/Introduction

Unable to start service vxvm-fstab-automount.service after upgrade from VRTSvxvm 7.1.0.100 to 7.1.0.200 or 7.1.0.300 preventing the vxfs filesystems from mounting automatically after a reboot.

Error Message

# systemctl status vxvm-fstab-automount.service
Unit vxvm-fstab-automount.service could not be found.

Additional Information

ETrack: 3938152