Skip to main content
NetApp Knowledge Base

ESX hosts and Virtual Machines are not able to read the virtual machine lock file when Varonis software is used

Views:
269
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

  • Product Model: FAS3220
  • OS: Data ONTAP 8.2.2P1 Cluster-Mode
  • VMware vSphere
  • Varonis Software

Issue

ESX hosts and Virtual Machines (VMs) are unable to read the vm lock file. The following "NFSLock" error messages are reported in the vmkernel.log on the the ESX host(s):

2015-02-26T06:03:11.000Z cpu12:36143)WARNING: NFSLock: 438: Cannot read lock file .lck-14350c0400000000: status 195887194 counter 4
2015-02-26T06:03:11.000Z cpu17:35598)WARNING: NFSLock: 438: Cannot read lock file .lck-194e360400000000: status 195887194 counter 4
2015-02-26T06:03:11.000Z cpu12:36143)NFSLock: 2941: failed to get lock on file protectedlist 0x410a96c8e4a0 on na-netapp-nfs1.netapp.edu (10.0.10.4): Busy
2015-02-26T06:03:11.000Z cpu17:35598)NFSLock: 2941: failed to get lock on file protectedlist 0x410a96cdf630 on na-netapp-nfs1.netapp.edu (10.0.10.4): Busy
2015-02-26T06:03:11.096Z cpu24:35826)NFSLock: 2941: failed to get lock on file host-970-poweron 0x410a96c97030 on na-netapp-nfs1.netapp.edu (10.0.10.4): Permission denied

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support