VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
Known issue: Migration complete but Maintenance
Mode not entered
Note that the vsan.resync_dashboard command may not display the full
information about a resynchronization activity. Therefore if a host in the Virtual
SAN cluster is placed into maintenance mode, and full data migration is requested,
but is still in progress when the vsan.resync_dashboard reports no bytes to
sync, it could well mean that other objects, for example templates, are still
resync’ing.
> vsan.resync_dashboard ie-vsan-01
2014-11-06 12:07:45 +0000: Querying all VMs on VSAN ...
2014-11-06 12:07:45 +0000: Querying all objects in the system from cs-ie-h01.ie.local ...
2014-11-06 12:07:45 +0000: Got all the info, computing table ...
+-----------+-----------------+---------------+
| VM/Object | Syncing objects | Bytes to sync |
+-----------+-----------------+---------------+
+-----------+-----------------+---------------+
| Total | 0 | 0.00 GB |
+-----------+-----------------+---------------+
The following commands will help check if this is the case:
vsan.disks_stats
First, use vsan.disks_stats on the host that is being placed into maintenance
mode. Check for any disks that still have a significant amount of used space and a
number of components greater than 0. Note that display name of the disk. In the
example below, cs-ie-03.ie.local is the host placed into maintenance mode.
> vsan.disks_stats 0
+--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+
| | | | Num | Capacity | | | Status |
| DisplayName | Host | isSSD | Comp | Total | Used | Reserved | Health |
+--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+
| naa.600508b1001c9c8b5f6f0d7a2be44433 | cs-ie-h03.ie.local | SSD | 0 | 186.27 GB | 0 % | 0 % | OK (v1) |
| naa.600508b1001cd259ab7ef213c87eaad7 | cs-ie-h03.ie.local | MD | 1 | 136.50 GB | 16 % | 0 % | OK (v1) |
| naa.600508b1001ceefc4213ceb9b51c4be4 | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) |
| naa.600508b1001cb11f3292fe743a0fd2e7 | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) |
| naa.600508b1001c9b93053e6dc3ea9bf3ef | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) |
| naa.600508b1001c2b7a3d39534ac6beb92d | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) |
| naa.600508b1001c1a7f310269ccd51a4e83 | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) |
+--------------------------------------+--------------------+-------+------+-----------+------+----------+---------
vsan.disk_object_info
In the output above, there is only one component left on the disk in question. All
other disks are empty on that host. Next, use the vsan.disk_object_info to see
what objects and components are still on the disk, using the display name from the
previous command as an argument.
> vsan.disk_object_info ie-vsan-01 naa.600508b1001c79748e8465571b6f4a46
Physical disk naa.600508b1001c79748e8465571b6f4a46 (52191bcb-7ea5-95ff-78af-
2b14f72d95e4):
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 9 3