VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
The same information can be retrieved from the vsan.resync_dashboard RVC
command. This is available in both 5.5 and 6.0 versions:
vsan.resync_dashboard
> vsan.resync_dashboard 0
2014-11-28 15:26:42 +0000: Querying all VMs on VSAN ...
2014-11-28 15:26:42 +0000: Querying all objects in the system from cs-ie-h02.ie.local ...
2014-11-28 15:26:43 +0000: Got all the info, computing table ...
+-------------------------------------------------------------------------+-----------------+---------------+
| VM/Object | Syncing objects | Bytes to sync |
+-------------------------------------------------------------------------+-----------------+---------------+
| vsan-022 | 1 | |
| [vsanDatastore] 89ae3e54-6495-85f6-9b6b-001b21168828/vsan-022_1.vmdk | | 1.00 GB |
| vsan-013 | 1 | |
| [vsanDatastore] f0713e54-2071-7be0-d570-001b21168828/vsan-013.vmdk | | 0.68 GB |
| vsan-009 | 1 | |
| [vsanDatastore] 1d713e54-9c80-4c2c-03de-001b21168828/vsan-009_1.vmdk | | 0.97 GB |
| vsan-008 | 1 | |
| [vsanDatastore] 1d713e54-b8d5-dd1d-b144-001b21168828/vsan-008.vmdk | | 0.68 GB |
| vsan-007 | 2 | |
| [vsanDatastore] d3703e54-24be-0d86-06e0-001f29595f9f/vsan-007.vmdk | | 0.68 GB |
| [vsanDatastore] d3703e54-24be-0d86-06e0-001f29595f9f/vsan-007_1.vmdk | | 0.95 GB |
| vsan-010 | 1 | |
| [vsanDatastore] 77713e54-04b3-7214-f997-001b21168828/vsan-010.vmdk | | 0.65 GB |
+-------------------------------------------------------------------------+-----------------+---------------+
| Total | 7 | 5.61 GB |
+-------------------------------------------------------------------------+-----------------+---------------+
>
However, there are also some useful RVC commands to get a more granular state of
the recovery/resyncing process.
vsan.vm_object_info
This command displays the state of individual VM objects. If you look closely at this
VM Namespace object (referred to as the Namespace directory below), the Witness
component is shown as ABSENT and STALE in the last line of the output.
> vsan.vm_object_info 1
VM vsan-002:
Namespace directory
DOM Object: 10703e54-40ab-2706-b9cd-001f29595f9f (v1, owner: cs-ieh04.ie.local,
policy: forceProvisioning = 0, hostFailuresToTolerate = 1,
spbmProfileId = VSANDefaultProfileId, proportionalCapacity = [0, 100],
spbmProfileGenerationNumber = 0, cacheReservation = 0, stripeWidth = 1)
RAID_1
Component: 7e8c7454-d7b2-6ec6-b44b-001f29595f9f (state: ACTIVE (5), host:
cs-ie-h02.ie.local, md: naa.600508b1001c07d525259e83da9541bf, ssd:
naa.600508b1001c577e11dd042e142a583f,
usage: 0.2 GB)
Component: be937454-22a0-e950-fb7d-001b21168828 (state: ACTIVE (5), host:
cs-ie-h01.ie.local, md: naa.600508b1001c79748e8465571b6f4a46, ssd:
naa.600508b1001c61cedd42b0c3fbf55132,
usage: 0.2 GB)
Witness: c3567854-4aee-aba7-6733-001b21168828 (state: ABSENT (6), csn:
STALE (78!=79), host: LSOM object not found)
Disk backing: [vsanDatastore] 10703e54-40ab-2706-b9cd-001f29595f9f/vsan-
002.vmdk
The STALE state is reflective of the fact that changes have occurred in the
configuration since the underlying device failed. As you can see, there is no
reference to a host, magnetic disk (md) or solid-state disk (ssd). Instead, we see
LSOM (Local Storage Object Manager) object not found. This is not a permanent
failure or else the status would be DEGRADED. Since it absent, Virtual SAN believes
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 1 5 0