Hi,
I experience a strange issue. I try to test a storage outage DR plan.
I have one vSphere 5.1 (1117900) cluster with VMFS datastores stored on an EMC storage array (VNX5100). Some of these datastores are replicated on a second array with array replication tool (MirrorView/S)
I tried this case : stop I/O with first array (remove lun from storage group) with powered on virtual machine (with disk I/O traffic generated with a simple file copy in Windows Explorer).
After this, I stopped all VMs which was stored on the removed datastore and start a rescan all lun. Datastore disappear from vSphere Client and VMs are marked as inactive.
I removed the permanent device lost entries and reboot the two nodes.
I promoted the LUN in the second array and I add the first node cluster to the storage group.
I started a Rescan all LUN and the devices are correctly listed and mounted but not the VMFS volume.
When I use this command : esxcli --server vcenterserver --vihost node1 --passthroughauth storage vmfs snapshot list
51befee9-f600f51d-9948-90b11c3bb4e2
Volume Name: DATASTORE01
VMFS UUID: 51befee9-f600f51d-9948-90b11c3bb4e2
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
I try many things but the datastore is detected as a snapshot.
I tried this : VMware KB: vSphere handling of LUNs detected as snapshot LUNs
but adding the datastore (using Keep Existing Signature) fail to resolve VMFS volume. Another strange things: The name of the datastore isn't detected by the wizard.
Any idea why ?