Microsoft has released (another) update overnight (what a week!!!) that deals with a Hyper-V scenario. This one is for when a Hyper-V host may be unable to reconnect to the Windows Server 2012 Cluster Scale-Out File Server (SOFS) share after an unplanned failover of one of the SOFS nodes.
Once again, this is niche. I’ve done many graceful and ungraceful shutdowns of SOFS nodes (both virtual and physical) over the past 18 or so months and not seen this issue.
Consider the following scenarios.
- You deploy file storage by using Failover Clustering Scale-Out File Server shares in Windows Server 2012.
- An unexpected error causes the Cluster service process (clussvc.exe) to stop.
In this scenario, you may receive I/O errors instead of failing over to a working cluster node.
- You deploy Windows Server 2012 Hyper-V hosts that run virtual machines that are stored on Failover Clustering Scale-Out File Server shares in Windows Server 2012.
- An unplanned failover causes the Scale-Out File Server to move to another node.
In this scenario, the Hyper-V host may be unable to reconnect to the share. This causes the virtual machines to become unresponsive and to enter a critical state.
A supported hotfix is available from Microsoft Support.