Differences

This shows you the differences between two versions of the page.

--- vmware:vmdklock [2015/02/25 15:22] – created naccad
+++ vmware:vmdklock [2015/02/25 15:26] (current) – naccad
@@ Line 5: / Line 5: @@
 Well, the good news is that this is relatively easy to do, at least under block storage.
-  - Which ESX is locking that file?
+  * Which ESX is locking that file?
 Remember that a VMDK has 2 parts: descriptor and data, the descriptor is rarely locked, you need to focus on the data portion, which has a file name ending in -delta.vmdk or -flat.vmdk
@@ Line 21: / Line 21: @@
 len 4294967296, nb 4096 tbz 3897, cow 0, zla 3, bs 1048576 vmkernel: 0:11:33:16.169
 </code>
+Focus on that line: <code>4aa5c319-7272c09a-3976-00221925665d</code>
+The last part of it <code>00221925665d</code> is the MAC address of one of the pNICs on one of the ESX servers.
+  * SSH into that host:
+Now that we know the MAC address, we need to find out which ESX host has it, you can get that through your switch ARP table or you can simple check the Configuration->Network Adapters page, the NIC does have to be in use so be careful. Once you find out the ESX host, ssh into that one.
+  * What process is doing the locking?
+This is where 'lsof' comes in handy, lsof stands for List Open File, all we have to do is this:
+<code>lsof -n | grep <FILENAME></code>
+Now you will have the process ID and some other related info, if it is a VMX process, check the VM, if it is vpxa for example, restart it.
+Good luck