| Previous | Next |
| ERROR_LOG_CLIENT_NOT_REGISTERED | ERROR_LOG_CONTAINER_READ_FAILED |
ERROR_LOG_FULL_HANDLER_IN_PROGRESS
A previous managed log-full request is still active
ClfsMgmtHandleLogFileFull attempts to make log space available. According to Microsoft, it first tries to add containers under the growth, new-container-size, and maximum-size policies; if growth cannot provide space, it can ask clients to advance log tails. The routine can complete asynchronously. A second request for the same client while that workflow is active returns the in-progress status instead of starting another concurrent recovery cycle.
Treat the condition as serialization and completion-state feedback, not as a reason to launch additional handlers. Track whether the first call returned pending and wait for the configured growth-complete callback. If the handler remains active indefinitely, inspect the callback path, tail-advance callbacks, and policy-limited container growth. Tight retry loops create noise and can obscure the original full condition. The client should resume normal writes only when the management completion path reports the resulting log-space state.
What to inspect
- Keep one in-flight log-full request per registered managed client.
- Trace the growth-complete callback and any tail-advance callbacks invoked by CLFS management.
- Investigate stuck growth or pinned tails instead of repeatedly calling the handler.
References
- Microsoft: ClfsMgmtHandleLogFileFull growth and tail-advance workflow
- Microsoft: ClfsLogGrowthCompleteCallback and asynchronous log-full completion
- Microsoft: CLFS management policy types
Looking for a different code? Search another status or error code.