MountV resource fails to offline and appears to hang in Veritas Storage Foundation for Windows
VCS WARNING V-16-10051-9023 MountV:MountResourceName_MountV: offline:Failed to lock volume [2:5]
By default, a MountV resource cannot be taken offline if a handle remains on the volume that it monitors.
To see if that is the case the %VCS_HOME%\log\MountV_A.txt log file will show if it has failed to lock the volume during offline.
- haconf -dump -makero (this saves and closes the cluster configuration)
- hastop -local -force (this stops the cluster service forcibly without offlining any resources that are online on the node)
- hastart (this starts the cluster service and, after a few seconds, the gui reconnects)
Now the MountV resources will be back to an "Online" status with no pending actions. You can now change the Force Unmount parameter to ALL at the MountV resource properties and retry the offline/switch or stop the process that has a handle on the volume then re-offline the resource again.
WARNING: ForceUnmount = ALL results in a volume being taken offline forcibly even when a write handle exists. This may result in file system corruption so it should be used with caution. Only enable this option if you are sure that no application or user are writing to the volume and have backups of data available to restore should it becomes unrecoverable.
If the MountV constantly ends up failing due to an open handle, we recommend you to try a Microsoft utility called handle.exe to determine what process is maintaining a handle on a volume. Other third-party utilities, such as Process Explorer and OH.exe can be used as well. (Please note that handle.exe may fail to complete if the HAD is running. So you may need to stop the HAD using the same command as above in step 2 prior to running this utility.)
How MountV reacts to a handle depends on the value of the ForceUnmount attribute in the resource properties: