| Previous | Next |
| ERROR_LOG_TAIL_INVALID | ERROR_COULD_NOT_RESIZE_LOG |
ERROR_LOG_FULL
The active CLFS log has exhausted reclaimable space
CLFS log space is governed by physical containers, base/tail positions, reservations, and management policies. A log can become full even when the volume still has free bytes: old extents may be pinned, the archive tail may not have advanced, reservations may consume capacity, or maximum-size policy may prevent adding another container. This is different from marshalling buffer exhaustion in ERROR_LOG_BLOCKS_EXHAUSTED.
Query log metadata, container count and size, installed management policies, archive state, and outstanding reservations. If a managed client is registered, ClfsMgmtHandleLogFileFull first attempts growth according to policy and then can request clients to advance their tails. The durable fix depends on what pins the log. Increasing the maximum alone can postpone recurrence without repairing a stalled checkpoint, archive, or reservation-release path.
What to inspect
- Measure physical log size, free log space, base/tail positions, and outstanding reservations together.
- Check maximum-size and auto-grow policy before assuming disk capacity is the limit.
- Use the managed log-full workflow or advance the responsible client tail only after its recovery data is no longer needed.
References
- Microsoft: ClfsMgmtHandleLogFileFull growth and tail-advance workflow
- Microsoft: CLFS management policy types
- Microsoft: ClfsLogGrowthCompleteCallback and asynchronous log-full completion
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
Looking for a different code? Search another status or error code.