| Previous | Next |
| STATUS_LOG_CLIENT_NOT_REGISTERED | STATUS_LOG_CONTAINER_READ_FAILED |
STATUS_LOG_FULL_HANDLER_IN_PROGRESS
STATUS_LOG_FULL_HANDLER_IN_PROGRESS is a concurrency result, not a second independent storage failure. CLFS management has already accepted a request to make space available for the registered client and may be growing the log or requesting tail movement.
The documented contract is to wait for the client growth-completion callback before issuing another full-log handling request for that client. Retrying immediately produces duplicate control traffic without creating additional capacity.
What to inspect
- Correlate the status with the first full-log request, its managed-client identity, and the corresponding completion callback.
- Inspect growth policies, tail callbacks, and pinning state while the request is pending rather than starting another handler.
- Treat a completed handler that still cannot make space as evidence to investigate pins, reservations, limits, or archive retention.
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.