| Previous | Next |
| STATUS_RKF_DUPLICATE_KEY | STATUS_RKF_STORE_FULL |
STATUS_RKF_BLOB_FULL
The handle-specific RKF record reached its capacity
RKF associates a bounded metadata blob with a handle so state required for later recovery can be persisted. This status is local to that handle record: the overall store may still have capacity, but no additional data can be appended to the current blob. It therefore differs from STATUS_RKF_STORE_FULL.
The immediate cause is usually an attempt to persist more metadata than the format or implementation allows, repeated attachment of records, or a component-version mismatch that writes an unexpected amount of state. Deleting unrelated files or expanding the data volume does not change this fixed record limit.
What to inspect
- Record the size and type of each metadata element added to the handle before the failure.
- Check for duplicate updates caused by replayed create or reconnect operations.
- Verify that SMB server, clustering, and filesystem components are at compatible servicing levels.
- Compare with a successful handle of the same workload to find unexpected extra state.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: RKF_BYPASS_ECP_CONTEXT
- Microsoft: SMB 3 file server features
- Microsoft Open Specifications: durable handle request v2
Looking for a different code? Search another status or error code.