How to correct fstab file locked by vxsvc process

From Wiki-UX.info
Jump to: navigation, search


Abstract[edit]

This article explains how to unlock the /etc/fstab file system locked by the vxsvc process

Problem Symptom[edit]

Running the mount -a command reports and error indicating that /etc/fstab file cannot be locked.

For example:

# mount -a 
mount: cannot lock /etc/fstab; still trying ... 
mount: cannot lock /etc/fstab; still trying ... 
mount: cannot lock /etc/fstab; still trying ... 
mount: cannot lock /etc/fstab; still trying ...

After checking with fsuser and ps commands, found that the vxsvc is the process using the fstab file:

# fuser /etc/fstab
3388o

# ps -ef | grep [3]388
root  3388     1  0  Jul 18  ?        2777:49 vxsvc -e

Solution[edit]

The vxsvc is the server process of the VEA environment. It is JAVA based product daemon process. You can safely kill and restart it. Look at /sbin/init.d/isisd to familiarize with other processes related with the VEA environment.

Running /opt/VRTSob/bin/vxsvcctrl restart will restart the vxsvc process. That should release any CPU resources capture by the process too.

Reference[edit]

Authors[edit]