| Previous | Next |
| STATUS_LOG_TAIL_INVALID | STATUS_LOG_MULTIPLEXED |
STATUS_LOG_FULL
STATUS_LOG_FULL means the physical CLFS log has exhausted space for the requested work. It is not simply a statement about free bytes on the volume: the relevant capacity is the set of usable containers after tail, archive, reservation, and management-policy constraints are applied.
For a managed log, CLFS can try to add containers or request tail movement. That distinguishes this result from STATUS_LOG_PINNED, where retained data prevents recycling, and from STATUS_LOG_FULL_HANDLER_IN_PROGRESS, where the managed response is already running.
What to inspect
- Record total and free log space, current base and tail LSNs, container inventory, archive mode, and outstanding reservations.
- Determine whether the caller is a registered managed client before asking CLFS management to grow the log or advance client tails.
- Do not delete individual containers to make room; reconcile the physical-log state through documented CLFS container and archive operations.
References
- Microsoft: ClfsMgmtHandleLogFileFull and full-log handling
- Microsoft: CLFS containers, tail pinning, and managed clients
- Microsoft: container, reservation, append, and flush APIs
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.