Failed write command to write-quiesced partition in VMware ESXi.
search cancel

Failed write command to write-quiesced partition in VMware ESXi.

book

Article ID: 302436

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • vCenter/vSphere Client reports errors similar to:

    ScsiDeviceIO: 3075: Failed write command to write-quiesced partition naa.XXXXXX

  • The vmkernel or messages logs contain entries similar to:

    cpu16:4971)ALERT: ScsiDeviceIO: 3075: Failed write command to write-quiesced partition naa.6006000000000000aa0aaa0000a0a000:1
    cpu16:4971)Fil3: 13359: Max retries (10) exceeded for caller Fil3_FileIO (status 'IO was aborted by VMFS via a virt-reset on the device')

Environment

VMware vSphere ESXi 6.#
VMware vSphere ESXi 7.#
VMware vSphere ESXi 8.#

Cause

This message is logged, usually for write operations, when an ESX/ESXi host needs to stop I/O going to a device/LUN. A Virtual Device Reset is used to stop the I/O to maintain VMFS data integrity.

Resolution

To resolve this issue, you must investigate the reason why the host issued the Virtual Device Reset.

 
Typically, there are SCSI or other storage related errors before the virt-reset error message. These errors indicate the reason why the host needed to stop the I/O.
 
Here is an example of the errors that may precede a virt-reset condition:

2010-03-19T05:11:36.873Z cpu8:4104)ScsiDeviceIO: 2316:Cmd(0x412401bede80) 0x2a, CmdSN 0x17af1 to dev "naa.60060160360########8e111" failed H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2010-03-19T05:11:38.943Z cpu12:4108)ScsiDeviceIO: 2288:Cmd(0x412440f9b240) 0x8a, CmdSN 0x17af2 to dev "naa.60060160360########aef30248e111" failed H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
2010-03-19T05:11:38.943Z cpu20:19244)WARNING: J3: 2644: Error committing txn callerID: 0xc1d00006 to slot 0: IO was aborted by VMFS via a virt-reset on the device
 
In the above example, the I/O is being aborted as there is no response from the fabric or storage array to I/O requests (likely an underlying storage issue). This results in the virt-reset as I/O needs to be stopped on the VMFS file system.



Additional Information

Powered by Wolken Software