Identifying a severely overloaded storage
When storage is severely overloaded, commands are aborted because the storage subsystem is taking far too long to respond to the commands. The storage subsystem has not responded within an acceptable amount of time, as defined by the guest operating system or application. Aborted commands are a sign that the storage hardware is overloaded and unable to handle the requests in line with the host's expectations.
The number of aborted commands can be monitored by using either vSphere Client or resxtop, as follows:
From the vSphere Client, monitor disk command aborts
From
esxtop, monitor ABRTS/s
Getting ready
To step through this recipe, you will need one or more running ESXi Servers, a vCenter Server, a working installation of vSphere Client, and a SSH Client (such as Putty). No other prerequisites are required.
How to do it…
To monitor the disk command aborts using vSphere Client you need to follow the proceeding steps:
Open up vSphere Client.
Log in to the...
