VMware Cloud Community
Solfoit1
Contributor
Contributor
‎06-13-2016 06:36 AM

vmkernel log nfslock messages

Hello,

Can anyone tell me what the following error message mean and how to resolve this issue?

       

server 12016-05-2611:3:25.407NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 22016-05-2812:9:12.222NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 32016-05-3118:21:6.663NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 42016-06-0123:38:12.255NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 52016-06-026:46:31.837NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 62016-06-047:18:26.202NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 42016-06-056:6:3.413NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 62016-06-0821:27:34.917NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 52016-06-0911:39:39.99NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 42016-06-0913:18:21.225NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 72016-06-1023:32:51.717NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 22016-06-1023:32:51.717NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 82016-06-1023:32:51.717NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 82016-06-1023:32:51.718NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 92016-06-1023:32:51.839NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 92016-06-1118:33:13.421NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 32016-06-1122:35:26.451NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle
server 82016-06-133:20:40.695NFSLock1772 Failed to create lock info for lock file .lck-e265000000000000 Stale file handle

thanks in advance

Greetings

0 Kudos
2 Replies
christianZ
Champion
Champion
‎06-14-2016 12:47 AM

Hi,

some information here:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10079... Locking

Reg

Chris

0 Kudos
BigBjorn
Enthusiast
Enthusiast
‎10-05-2016 11:46 PM

Hi!

Did you ever find out what this meant? I have these issues too.


No obvious issue but VMware Log Insight is alerting on this on two different NFS locks. It's only ESXi hosts connected to NetApp storage via NFS have this logged. We have also other clusters with different NFS storage that are not affected.

esxi-00001 vmkernel: cpu1:34222)NFSLock: 1772: Failed to create lock info for lock file .lck-735c000000000000 : Stale file handle

and

esxi-00004 vmkernel: cpu28:34224)NFSLock: 2966: failed to get lock on file access 0x430479151ce0 on 192.168.168.168 (192.168.168.168): Busy

Any suggestions is appreciated.

Thanks

/B

EDIT: The ESXi have the correct parameters set according to NetApp best practices. Also, the KB mentioned in this thread did not give me any clues.

0 Kudos