Skip to main content
NetApp Knowledge Base

Cannot power on Vsphere VM due to stale NFSv4.1 locks

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

Applies to

  • vSphere 6.5 or later
  • ONTAP 9
  • NFS

Issue

A virtual machine cannot be powered on after:

  • the ESXi host has crashed 
  • A power on attempt for the VM occurs on another host.

The vmware.log of the VM shows:

2017-07-10T16:25:35.466Z| Worker#0| I125: OBJLIB-FILEBE : FileBEOpen: can't open '/vmfs/volumes/abcedfg-gfeagcf-0000-000000000000/NAS/NAS_1.vmdk' : Connection timed out (7208964).

Failed to add disk scsi0:1. File system specific implementation of OpenFile[file] failed 110 (Connection timed out) Cannot open the disk '/vmfs/volumes/0280fba4-5a71fa92-0000-000000000000/2d8ba3dd-ca26-4de9-aebc-b7a7dedb17c1/0eda5be20eb04b4e906f19fc3e8119bb.vmdk' or one of the snapshot disks it depends on. Failed to power on scsi0:1

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.