09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Flash Cache SSD is pulled unexpectedly from ESXi host<br />

When an SSD (acting as the cache tier) is pulled without decommissioning it, all the<br />

Virtual SAN components residing in that disk group go ABSENT and are inaccessible.<br />

In other words, if the flash tier SSD is removed, it will appear as a removal of the<br />

flash device as well as all associated magnetic disks (in hybrid configurations) or<br />

flash devices (in all-flash configurations) providing backing capacity.<br />

Expected behaviors:<br />

If the VM has a policy that includes NumberOfFailuresToTolerate=1 or greater,<br />

the VM’s objects will still be accessible.<br />

Disk group and the disks under the disk group states will be marked as<br />

ABSENT and can be verified via the vSphere web client UI.<br />

All in-flight I/O is halted while Virtual SAN reevaluates the availability of the<br />

objects without the failed component(s) as part of the active set of<br />

components.<br />

If Virtual SAN concludes that the object is still available (based on available<br />

full mirror copy and witness/votes), all in-flight I/O is restarted.<br />

All components residing in this disk group will be marked as ABSENT in the<br />

UI.<br />

The typical time from physical removal of the drive, Virtual SAN processing<br />

this event, marking the component ABSENT halting and restoring I/O flow is<br />

approximately 5-7 seconds.<br />

When the same SSD is placed back on the same host within 60 minutes, no<br />

new objects will be re-built.<br />

When the timeout expires (default 60 minutes), components on the impacted<br />

disk group will be rebuilt elsewhere in the cluster, if capacity is available.<br />

If the VM Storage Policy has NumberOfFailuresToTolerate=0, the VMDK will<br />

be inaccessible if one of the VMDK components (think one component of a<br />

stripe or a full mirror) exists on disk group whom the pulled flash tier SSD<br />

belongs to. To restore the VMDK, the same SSD has to be placed back in the<br />

ESXi host. There is no option to recover the VMDK.<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 / 64

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

Saved successfully!

Ooh no, something went wrong!