CLUSTER_CLUSPORT_STATUS_IO_TIMEOUT_LIVEDUMP
Code: 0x179 (377)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x0179 (377)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x0179 (377)
Parameters
| Parameter | Description |
|---|---|
| 1 | IRP that ran into the timeout. |
| 2 | Reserved. |
| 3 | Reserved. |
| 4 | Reserved. |
Description
The CLUSTER_CLUSPORT_STATUS_IO_TIMEOUT_LIVEDUMP live dump has a value of 0x00000179. This indicates that SMB client on the initiator node complains that an IO to a target node is taking too long and fails all IOs with STATUS_IO_TIMEOUT.
Cause
SMB client on the initiator node complains that an IO on target node is taking too long and fails all IOs with STATUS_IO_TIMEOUT.
In response to that, the cluster initiator captures live dump on the initiator node so we can analyze what IO is taking time.
Additional information is available in the dump's secondary data streams.
(This code can never be used for a real bug check; it is used to identify live dumps.)
Resolution
See Also
Troubleshooting Hangs Using Live Dump (Blog)
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0x179 | 78.11011 | %1 |
| kernel32.dll | 0x179 | 1011 | The file is not in sync with the cloud. |
| webservices.dll | 0x179 | 78.11011 | The text '%1' was found, but not expected. |
| 3 entries | |||