Latest Posts



Translate

Total Pageviews

Wednesday, 22 August 2012

VMFS Volume is Locked

Details

The event indicates that a VMFS volume on the ESX/ESXi host is currently locked due to an I/O error.

For example, 
if naa.60060160b3c018009bd1e02f725fdd11:1 represents one of the partitions used in a VMFS volume, then the following is displayed if the VMFS volume is inaccessible:

Volume on device naa.60060160b3c018009bd1e02f725fdd11:1 locked, possibly because remote host 10.17.211.73 encountered an error during a volume operation and couldn’t recover.
If this occurs, the VMFS volume (and the virtual machines residing on the affected volume) are unavailable to the ESX/ESXi host

Solution

To correct this issue you will need to login to the ESX/ESXi console:
Log in to the terminal of the VMware ESX or ESXi host and run the following commands:
  1. Break the existing LVM lock on the datastore:
    # vmkfstools –B <vmfs device>
    Note: You can also use the parameter --breaklock instead of -B with the vmkfstools command.
    From the error message above, the following command is used:

    # vmkfstools -B /vmfs/devices/disks/
    naa.60060160b3c018009bd1e02f725fdd11:1

    The following output will be displayed:

    VMware ESX Question:
    LVM lock on device /vmfs/devices/disks/naa.60060160b3c018009bd1e02f725fdd11:1 will be forcibly broken. Please consult vmkfstools or ESX documentation to understand the consequences of this.

    Please ensure that multiple servers aren't accessing this device.

    Continue to break lock?
    0) Yes
    1) No

    Please choose a number [0-1]:

  2. Enter 0 to break the lock.

  3. Re-read and reload VMFS datastore metadata to memory:

    # vmkfstools –V
  4. From the vSphere UI, Refresh the Storage Datastores View under Configuration tab.
Source:-