09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />

this device might come back, so this situation could be a result of a host reboot or a<br />

disk that was offlined or ejected from the host. Virtual SAN will wait 60 minutes<br />

before rebuilding any of these components by default.<br />

Note: The above output is taken from version 5.5. vsan.vm_object_info is different<br />

in Virtual SAN version 6.0. In the 6.0 version, a new field is included which includes<br />

the vote count of the component, as shown here:<br />

Component: b91dd354-a3ed-a07c-c799-b8ca3a70ba70 (state: ACTIVE (5), host:<br />

10.155.60.18, md: naa.5000c500581adacb, ssd: naa.55cd2e404b4d06e4, votes: 1,<br />

usage: 0.4 GB)<br />

vsan.resync_dashboard<br />

If the previous situation where a device is ABSENT continues for 60 minutes (by<br />

default, but tunable), Virtual SAN will rebuild the affected components of the<br />

ABSENT device. The command vsan.resync_dashboard will display the resyncing<br />

of the components that are being rebuilt elsewhere in the cluster. Using this<br />

command, it is possible to tell how many bytes are left to sync for that particular<br />

VM/Object.<br />

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 1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!