| Previous | Next |
| STATUS_LOG_INVALID_RANGE | STATUS_LOG_READ_CONTEXT_INVALID |
STATUS_LOG_BLOCKS_EXHAUSTED
STATUS_LOG_BLOCKS_EXHAUSTED concerns the memory-side marshalling area that CLFS uses before log I/O blocks reach stable storage. It is not the same condition as a full physical log: a log can have recyclable or addable container capacity while the caller has exhausted the buffers available for marshalling.
CLFS makes appended records visible to other marshalling contexts according to append and flush behavior. Outstanding I/O, retained buffers, or undersized marshalling-area limits are therefore relevant to this status in a way that a simple disk-capacity check is not.
Inspect the marshalling side of the pipeline
- Record the marshalling-area configuration, concurrent append activity, and any outstanding asynchronous operations.
- Differentiate this code from
STATUS_LOG_FULLorSTATUS_LOG_FILE_FULLbefore adding containers or moving tails. - Ensure callers complete or retire their CLFS contexts according to the API contract before increasing memory-side limits.
References
- Microsoft: CLFS concepts and marshalling
- Microsoft: CLFS API reference
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.