Lock corruption detected at offset

[cavsystems]

Anyone can be nice and explain:

\[root@vm2 ASP]# rm ASP_1-flat.vmdk

rm: remove regular file `ASP_1-flat.vmdk'? ^[[A

\[root@vm2 ASP]# rm ASP_1-flat.vmdk

rm: remove regular file `ASP_1-flat.vmdk'? y

rm: cannot remove `ASP_1-flat.vmdk': Invalid argument

\[root@vm2 ASP]# rm ASP_1-flat.vmdk

rm: remove regular file `ASP_1-flat.vmdk'? y

rm: cannot remove `ASP_1-flat.vmdk': Invalid argument

\[root@vm2 ASP]# rm ASP_1-flat.vmdk

rm: remove regular file `ASP_1-flat.vmdk'? y

rm: cannot remove `ASP_1-flat.vmdk': Invalid argument

\[root@vm2 ASP]#

\[root@vm2 ASP]# tail /var/log/vmkernel

Sep 2 20:36:45 vm2 vmkernel: 0:00:04:03.526 cpu3:1033)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:36:47 vm2 vmkernel: 0:00:04:05.211 cpu1:1034)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:36:48 vm2 vmkernel: 0:00:04:06.238 cpu1:1034)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:36:50 vm2 vmkernel: 0:00:04:07.714 cpu3:1033)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:36:56 vm2 vmkernel: 0:00:04:14.206 cpu3:1033)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:37:02 vm2 vmkernel: 0:00:04:20.082 cpu3:1033)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:37:03 vm2 vmkernel: 0:00:04:21.333 cpu3:1033)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:37:19 vm2 vmkernel: 0:00:04:37.525 cpu3:1033)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:37:20 vm2 vmkernel: 0:00:04:38.402 cpu3:1033)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

Sep 2 20:37:21 vm2 vmkernel: 0:00:04:39.067 cpu3:1033)WARNING: FS3: 1575: Lock corruption detected at offset 0xea0000

\[root@vm2 ASP]#

[Michelle_Laveri]

Anyone can be nice and explain:

\[root@vm2 ASP]# rm ASP_1-flat.vmdk

rm: remove regular file `ASP_1-flat.vmdk'? ^[[A

\[root@vm2 ASP]# rm ASP_1-flat.vmdk

rm: remove regular file `ASP_1-flat.vmdk'? y

rm: cannot remove `ASP_1-flat.vmdk': Invalid

argument

\[root@vm2 ASP]# rm ASP_1-flat.vmdk

rm: remove regular file `ASP_1-flat.vmdk'? y

rm: cannot remove `ASP_1-flat.vmdk': Invalid

argument

\[root@vm2 ASP]# rm ASP_1-flat.vmdk

rm: remove regular file `ASP_1-flat.vmdk'? y

rm: cannot remove `ASP_1-flat.vmdk': Invalid

argument

\[root@vm2 ASP]#

\[root@vm2 ASP]# tail /var/log/vmkernel

Sep 2 20:36:45 vm2 vmkernel: 0:00:04:03.526

cpu3:1033)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:36:47 vm2 vmkernel: 0:00:04:05.211

cpu1:1034)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:36:48 vm2 vmkernel: 0:00:04:06.238

cpu1:1034)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:36:50 vm2 vmkernel: 0:00:04:07.714

cpu3:1033)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:36:56 vm2 vmkernel: 0:00:04:14.206

cpu3:1033)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:37:02 vm2 vmkernel: 0:00:04:20.082

cpu3:1033)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:37:03 vm2 vmkernel: 0:00:04:21.333

cpu3:1033)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:37:19 vm2 vmkernel: 0:00:04:37.525

cpu3:1033)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:37:20 vm2 vmkernel: 0:00:04:38.402

cpu3:1033)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

Sep 2 20:37:21 vm2 vmkernel: 0:00:04:39.067

cpu3:1033)WARNING: FS3: 1575: Lock corruption

detected at offset 0xea0000

\[root@vm2 ASP]#

I take it you have powered off the VM?

Does this affect just this VM or others?

Is there any reason why your using rm to remove files instead of say "delete from disk"?

Regards

Mike

[cavsystems]

Yes, I powered off the VM.

There are other that have this problem.

The machines are no longer registered, so I want to remove them.

Total machines 19, 2 have the problem.

[Michelle_Laveri]

mmm, lock errors would normally be associated with some sort of process error. Locks are used to protect the VMFS metadata from corruption - and transient locks are imposed and released at events such as power on/off of VMs, creating, deleting and growing files.

Sometimes I have seen although a VM appears to be powered in the Vi Client. The process associated with the VMX file is still running. Using ps -ef at the Service Console can help show this - and killall -9 can be used to terminate them...

There is also command-line switch on vmkfstools that can be used to send a manual "unlock" command.

To be honest with you I would suggest opening a SR with VMware on this - just to be safe.

Regards

mike