| Previous | Next |
| STATUS_CLUSTER_CSV_NO_SNAPSHOTS | STATUS_CLUSTER_CSV_INVALID_HANDLE |
STATUS_CSV_IO_PAUSE_TIMEOUT
CSV recovery did not finish within this file object’s allowed interval
STATUS_CSV_IO_PAUSE_TIMEOUT is tied to Cluster Shared Volume recovery and the timeout associated with the affected file object. Microsoft’s CSV troubleshooting guidance describes Event 5120 as an interruption in communication between a cluster node and a CSV. During storage-path recovery, CSV I/O can be paused or queued while a path is reestablished.
That makes the storage timeline central. Correlate the NTSTATUS with CSV events such as 5120 and 5142, storage Event 153, cluster network state, and MPIO or DSM path changes. A timeout at the file-object level can be the application-visible end of a much earlier SAN, iSCSI, Fibre Channel, SMB, or local storage interruption.
Increasing an application retry timeout may reduce symptoms but does not explain why CSV recovery exceeded its interval. Find the first path-loss or pause event and measure how long recovery actually took. If many nodes or CSVs fail together, look for shared fabric, controller, DSM, or network dependencies before blaming an individual virtual machine file.
What to inspect
- Cluster events 5120 and 5142, storage Event 153, and the first path or communication failure before the NTSTATUS.
- Affected CSV, node, file object, and measured pause-to-recovery duration.
- MPIO or DSM path states and whether failures share a controller, fabric, network, or storage array.
References
- Microsoft: Event ID 5120 CSV troubleshooting guidance
- Microsoft: Storage issues in Hyper-V and failover clusters
- Microsoft: Multipath I/O troubleshooting guidance
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.