| Previous | Next |
| STATUS_CLUSTER_CSV_VOLUME_NOT_LOCAL | STATUS_CLUSTER_CSV_AUTO_PAUSE_ERROR |
STATUS_CLUSTER_CSV_READ_OPLOCK_BREAK_IN_PROGRESS
A CSV read oplock break is still being processed
STATUS_CLUSTER_CSV_READ_OPLOCK_BREAK_IN_PROGRESS is a transient coordination result. An oplock break changes the caching or sharing assumptions for an open file object; CSVFS rejects this request instead of racing an unfinished break.
The useful question is not whether the file exists. Identify the handle and operation, then determine whether the caller can reopen or retry an idempotent request after the break completes. A retry loop that holds stale state or repeats a non-idempotent write can make the incident worse.
What to verify
- The file operation and whether a safe retry is idempotent.
- Cluster, CSVFS, application, backup, and antivirus activity at the same timestamp.
- Whether the affected handle was opened before a path, ownership, or metadata transition.
References
- Microsoft: Cluster Shared Volumes overview
- Microsoft: CSV Event ID 5120 guidance
- Microsoft: Get-ClusterLog
Looking for a different code? Search another status or error code.