Device or resource busy

A recently upgraded ESX system (3 hosts) had a SAN controller failover. This caused many VMs to die and get locked files. It's not only the disk files that are locked for these VMs, but also the vmx files, config files and everything. Other VMs on the same LUN (and hosts) are working fine.

# vmware -v

VMware ESX 4.0.0 build-164009

# more vmware.log

vmware.log: Device or resource busy

# cat notes.vmx

cat: notes.vmx: Device or resource busy

ls works fine and I can even create a new file within this directory that I can edit, read and delete just fine.  Unregistering/Reregistering the VM is not possible since even the vmx file is not readable.

A power outage has also caused everything to power down some while after this, so there are no hanging processes.

I've read a couple of postings (in the 3.5 forum, and I wonder why I can't find them anymore) suggest that one should connect a single ESX 3.0.2 server to the LUN to fix this.

Any other hints? Will try the 3.0.2 route now..

Lars