Skip to main content
NetApp Knowledge Base

Hyper-V VMs stops but did not automatically resume after failover when IO suspend due to wafl hung happens

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • Hyper-V 
  • SMB 3

Issue

  •  I/O was stopped for more than 10 minutes due to wafl hung. 
  • After the failover, I/O became available again, but Hyper-V did not automatically resume.
  • Hyper-V hosts showed SMB3 share was disconnected.
  • After rebooting hyper-V hosts, SMB3 share becomes  connected state.   

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.