| Previous | Next |
| STATUS_RKF_STORE_FULL | STATUS_RKF_ACTIVE_KEY |
STATUS_RKF_FILE_BLOCKED
Existing resume state is fencing access to the file
During transparent failover, the server must prevent a new open from racing with recovery of persistent handles that already own state on the file. RKF can temporarily fence the file until those handles are resumed, expired, or explicitly cleaned up. This protects ordering, locks, oplocks, and application I/O semantics across the interruption.
The status is therefore not equivalent to a permanent ACL denial. Retrying immediately from many threads can increase contention. The important question is whether the expected reconnect is still progressing or whether stale resume state is blocking the file beyond the configured durable-handle timeout.
What to inspect
- Correlate the file path with active, disconnected, and reconnecting SMB persistent handles.
- Check the durable-handle timeout returned by the server and the elapsed failover time.
- Inspect witness, cluster, network, and SMBServer events for the client that owns the old handle.
- Allow recovery or timeout to complete before forcing a new open or administrative cleanup.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Open Specifications: durable handle request v2
- Microsoft Open Specifications: durable handle response v2
- Microsoft: Scale-Out File Server overview
Looking for a different code? Search another status or error code.