Issue:
The MountV resource for a volume using a folder mount (Mount Point) fails to come online in an InfoScale for Windows cluster. The following error will be seen in the %VCS_HOME%\log\MountV_A.txt log:

VCS WARNING V-16-10051-9020 MountV:<MountResName>:online:<mounted_folder_path> is not suitable for folder mount

Cause:
The InfoScale for Windows cluster is making a Windows API call to mount this folder, and Windows is returning an error because the folder being specified does not qualify to be used for a folder mount. The solution section below describes three different situations that can cause this.

Solution:
Below are three scenarios that can cause this and how each can be resolved:

Note: All scenarios described below require access to the folder being used for the Mount Point to determine and resolve the issue. Please ensure that the VMDg resource is online in the cluster as well as any MountV resources that the problem MountV resource may be dependent on (i.e. If the problem Mount Point is 'F:\Mount1', ensure that the 'F:\' MountV resource is online in the cluster)

1. The folder being used as the folder mount (as specified in the error message seen in the MountV_A.txt log) is not an empty directory; therefore, it cannot be used as a folder mount.

To verify and/or resolve this, perform the following steps:
 

a. Determine the file folder being used for the MountV resource that is failing by either checking the error in the MountV_A.txt log file which provides the path, or by viewing the properties of the MountV resource in the VCS Cluster Manager Java Console (Mount Path attribute).
 

b. Browse to this directory and determine whether or not it is an empty directory.
 

c. If the folder is not empty, either change the MountV resource properties to point to an empty directory or remove all contents from the directory currently specified so that no data exists inside the folder. Windows requires an empty directory to be used for Mount Points.
 

d. Once complete, the MountV resource should be able to online successfully.
 

e. If the directory is empty, see Scenario's 2 and 3 below.

2. An abrupt outage on the server occurred which left the folder being used for the Mount Point in a state where it thinks it is still a mounted volume; therefore, any attempt to mount to this folder fails. This may especially be seen in Global Clusters (GCO) when performing a fail-over between sites where replication is being used (i.e. Veritas Volume Replicator).
 

To verify and/or resolve this, perform the following steps:
 

a. Browse to the directory specified for the mount path. When attempting to open the file folder, the following error may be seen:
 

"<mounted_folder_path> refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location."
 

b. Right-click the file folder and select 'Properties'
 

c. Check the 'Type' value on the 'General' tab. If this states 'Mounted Volume', then the Operating System thinks that this folder is already being used as a file mount. If it shows File Folder, then this is not the issue and the remaining steps in scenario 2 can be skipped.
 

d. If certain this is not being used by another volume, and after verifying the directory is empty, open a command prompt and run the command: mountvol <mount_path> /D
 

Example: If the problem Mount Path is F:\Mount1, the command to run is: mountvol F:\Mount1 /D
 

e. After performing this, checking the 'Properties' of the file folder again will show a type of: 'File Folder'
 

f. Once complete, the MountV resource should be able to online successfully.

3. If dependencies are not set correctly in the cluster, it is possible that a folder mount MountV resource may attempt to online prior to the root volume it depends on becoming available.
 

For example, if my mount path was F:\Mount1, but this was not dependent on my MountV for the F:\ volume, the MountV mount point would fail because the F:\ volume was not available when it attempted to online.