Hi @all,

if I understood the first thread right, the problem is the vmdk or -flat.vmdk and not the .svwp file.

To fix vswp issues there are a lot of dirty methods available, move the file, delete the file or just chance the file in der .vmx.

But if the -flat.vmdk is locked, you will not have any chance to unlock the file with the available tools.

You can check it with touch: "touch /vmfs/volumes/VM-Store/guest_folder/guest-flat.vmdk"

if you get no output, everything is ok, but if you get a message like "invalid argument" the file ist locked.

We run in this problem after a crash of 1 ESX Server. After the Server comes up again we had about 30 locked files in the Store, we tried to restart all the ESX Server, hide the LUN and so on but nothing worked.

In our case the Problem is that the VMFS3 does not update the timestamp in dthe VMFS-Meta-data, normaly a file gets unlocked if the timestamp is older then 3 Seconds. In our case the Timestamp is older, but nothing happens.

bye

eazy