| Previous | Next |
| ERROR_LOG_CANT_DELETE | ERROR_LOG_START_OF_LOG |
ERROR_LOG_CONTAINER_LIMIT_EXCEEDED
The CLFS physical log cannot allocate another container
Containers are the physical files or streams that hold CLFS log data, and adding containers grows the physical log. The CLFS management sizing API documents a maximum of 1,024 containers for a log file. Reaching the container limit is therefore different from hitting a byte-size maximum or running out of disk space: the physical log has exhausted the supported number of container slots.
Enumerate the existing container count and inspect the management policies that control container size, growth rate, minimum size, and maximum size. A log that repeatedly adds small containers can reach the count ceiling earlier than a log using larger containers. Do not delete random container files to make room; containers must be removed through CLFS and only when the log state allows recycling or shrinking. Correct the policy or owner behavior that caused pathological growth, then use supported size-management operations.
What to inspect
- Count containers and compare the result with the CLFS log-size policy and 1,024-container limit.
- Review new-container size and auto-grow policy for excessive small-container growth.
- Shrink or recreate the log through CLFS management rather than removing files from the directory.
References
- Microsoft: AddLogContainer sizing and physical-log growth
- Microsoft: ClfsMgmtSetLogFileSizeAsClient and the 1,024-container limit
- Microsoft: CLFS management policy types
Looking for a different code? Search another status or error code.