| Previous | Next |
| STATUS_CLUSTER_CSV_NOT_REDIRECTED | STATUS_CLUSTER_CSV_SNAPSHOT_CREATION_IN_PROGRESS |
STATUS_CLUSTER_CSV_VOLUME_DRAINING
Meaning and context of STATUS_CLUSTER_CSV_VOLUME_DRAINING
Cluster Shared Volumes (CSV) is a feature of Failover Clustering first introduced in Windows Server 2008 R2 for use with the Hyper-V role. A Cluster Shared Volume is a shared disk containing an NTFS or ReFS (ReFS: Windows Server 2012 R2 or newer) volume that is made accessible for read and write operations by all nodes within a Windows Server Failover Cluster.
This enables a virtual machine (VM) complete mobility throughout the cluster as any node can access the VHD files on the shared volume. Cluster Shared Volumes simplifies storage management by allowing large numbers of VMs to be accessed off a common shared disk. CSV also increases the resiliency of the cluster by having I/O fault detection and recovery over alternate communication paths between the nodes in the cluster.
While CSV is not required for Live Migration of VMs, it reduces the potential disconnection period at the end of the migration since the NTFS file system does not have to be unmounted/mounted as is the case with a traditional cluster disk. This helps ensure seamless live migration since the physical disk resource does not need to be moved between nodes. CSV increases the chance that a live migration will complete within the TCP reconnect window and ensure a seamless operation to clients.
Native status interpretation for STATUS_CLUSTER_CSV_VOLUME_DRAINING
STATUS_CLUSTER_CSV_VOLUME_DRAINING is 0xC0130024, an NTSTATUS error value. AllStat describes it as “CSVFS is failing operation because it is in draining state.”. The first useful question is which native API, IRP, protocol operation, or subsystem in Failover Clustering state produced that status.
Debugging sequence for STATUS_CLUSTER_CSV_VOLUME_DRAINING
- Preserve STATUS_CLUSTER_CSV_VOLUME_DRAINING before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- Correlate STATUS_CLUSTER_CSV_VOLUME_DRAINING with ETW, Event Viewer, protocol traces, or a dump from the component that owns cluster / csv / volume / draining; do not diagnose from translated text alone.
- For kernel I/O, keep the device stack, IRP major/minor function, request parameters, completion routine, and the first component that completed the request with STATUS_CLUSTER_CSV_VOLUME_DRAINING.
Recovery considerations for STATUS_CLUSTER_CSV_VOLUME_DRAINING
A retry is appropriate only after the owner of STATUS_CLUSTER_CSV_VOLUME_DRAINING has changed the state described by “CSVFS is failing operation because it is in draining state.”, or when its contract explicitly marks the status as transient. If the value reports corruption, invalid format, access policy, or a lifecycle mismatch, preserve evidence and correct that cause before repeating the request.
Official references for STATUS_CLUSTER_CSV_VOLUME_DRAINING
Looking for a different code? Search another status or error code.