Unable to access filesystem for MSCS cluster nodes after vMotion
search cancel

Unable to access filesystem for MSCS cluster nodes after vMotion

book

Article ID: 317980

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

If virtual machine is part of a Microsoft Cluster Service (MSCS), you experience these symptoms:

  • The virtual machine loses filesystem access after vMotion.
  • In the virtual machine, you see NTFS system event 140.


Environment

VMware vSphere ESXi 6.0

Cause

Microsoft Cluster Service (MSCS) also known as Microsoft Failover Cluster, can see NTFS system event 140 during a vMotion of any node in the cluster. This may result in loss of access to the filesystem within the guest operating system.

Resolution

This issue is resolved in VMware ESXi 6.0, Patch Release ESXi600-201608001.
 
To work around the issue if you do not want to upgrade, change the path selection policy in ESXi 6.0 from Round-Robin to Fixed or Most Recently Used (MRU) based on storage array type.



Additional Information

For more information on various pathing policies that can used with VMware, see VMware Multipathing policies in ESXi/ESX