Unable to access file <unspecified filename> since it is locked

[haverer]

Hi,

I am running 2 ESX Hosts. On each host I was running just the 1 virtual machine (both of which connect to disks on the same SAN). I have now created another Virtual Machine to run on each host (4 virtual machines in total, 2 virtual machines on each host).

I have added the virtual disks into my new VM's (by using option 'use an existing virtual disk'). However when I try to power on my new Virtual Machines I am presented with the error:

"Unable to access file since it is locked"

On Host 1, I have powered off the 'old' Virtual Machine incase it was holding onto some files. I then powered up my new virtual machine and it works! However, I then go to power on the 'old' Virtual Machine and this has the same error!!

AARGH!!

[haverer]

Hi, unfortunately ESX Server 2 is being used so I wouldn't be able to restart this until after Production tonight.

Do you think that should do the trick? I will try it tonight. Thanks for your help

[haverer]

No. Bizarrely I don't have the snapshot option on VM1 'Take Snapshot' is greyed out. However I can take snapshots on VM2. I assumed this was to do with the SCSI Bus Sharing?

I have went onto 'Edit Settings' on VM3 (this is the VM on the other ESX Host) and noticed that both SCSI Controllers Bus Sharing is set to 'None'. Really surprised about this, I would have thought it would have had to be set to Physical for the RDMs on this as well so it could access the files on the SAN? Seems to work ok though

[haverer]

Yeh, I just set VM1 SCSI Bus Sharing to 'None' and it will allow me to take a snapshot now

[mbx369]

As of now, how many VMs have these same disks as RDM? And are all of them powered off?

~~~~~ To Live Is To Die ~~~~~

VCP3&4

[haverer]

As of now, 4 VMs:

ESX HOST 1: VM1 and VM2

ESX HOST 2: VM3 and VM4

All VMs are powered off with the exception of VM3

[haverer]

I changed the SCSI Bus Sharing back to 'None' on VM1 to try a few things. Then I changed it back to Physical and now getting the same error as Vm2 - SCSI controller is engaged in bus-sharing!! ARGH! I deleted the disks from VM2 and then tried VM1 again but same!!

[mbx369]

Any VMs that you intend to add RDM disks should be powered off. That includes the 1st VM you shared out.

Have you tried to power off VM#3, then configure what you need to on the others then power them on?

Hope that works.

Also, the mgmt-vmware service restart will not cause your VMs to be powered off. Just need to disable your HA cluster if your ESX hosts are in one.

This is a wierd problem, usually we might have missed out on a minor detail. Try to retrace back your steps.

Keep me posted on the outcome, it's 12am where I am now. Leaving office now bro.

Best of luck

~~~~~ To Live Is To Die ~~~~~

VCP3&4

[mbx369]

Hi Haverer,

so it it go?

~~~~~ To Live Is To Die ~~~~~

VCP3&4

[haverer]

Hi,

I managed to get all disks configured on VM2 and VM4. However, for this to work - I had to ensure VM1 and VM3 were both powered off! I couldn't power on all 4 VMs, otherwise I would get the 'Unable to access file since it is locked' error.

My setup is:

ESX HOST 1: VM1 and VM2

ESX HOST 2: VM3 and VM4

So I am guessing that you cannot have 2 VMs on the same Host running at the same time and accessing the SAN? Kinda defeats the purpose surely?

[mbx369]

Hi

Glad to hear it's working now. Yup, that's the max I guess, 2 nodes. We can only hope it increases in the near future.

Please awards points if this was useful.

~~~~~ To Live Is To Die ~~~~~

VCP3&4

[din123]

Hi all,

I also faced the same issue, it worked but the reason is not working is that,

bydefault iscsi device is in mode of paravirtulization, you have to turn it to lsi parellal mode. then only other iscsi will work.