vmware:vmdklock
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. | Well, the good news is that this is relatively easy to do, at least under block storage. | ||
- | | + | |
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 | 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: | len 4294967296, nb 4096 tbz 3897, cow 0, zla 3, bs 1048576 vmkernel: 0: | ||
</ | </ | ||
+ | |||
+ | Focus on that line: < | ||
+ | |||
+ | The last part of it < | ||
+ | |||
+ | * 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-> | ||
+ | |||
+ | * What process is doing the locking? | ||
+ | |||
+ | This is where ' | ||
+ | |||
+ | < | ||
+ | |||
+ | 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 | ||
vmware/vmdklock.1424877758.txt.gz · Last modified: 2015/02/25 15:22 by naccad