| Previous | Next |
| ERROR_LOG_RESERVATION_INVALID | ERROR_LOG_CONTAINER_LIMIT_EXCEEDED |
ERROR_LOG_CANT_DELETE
The CLFS log or container cannot be deleted now
CLFS exposes deletion of log streams and removal of physical containers as managed operations. The base log metadata and container set are related, and containers can hold active log extents. A delete can therefore fail for CLFS state reasons even when the caller has ordinary file-system delete permission. Treating the container as a standalone file and unlinking it directly bypasses the physical-log bookkeeping that CLFS maintains.
Identify whether the request targets a logical stream, the physical log, or a container. Check open log handles, active archive contexts, current container count, and whether the container still belongs to the active log. If the owning component is running, quiesce it through the supported service path before log maintenance. Also verify ACL and sharing failures separately: this error reports the CLFS delete operation, but the underlying environment can still contribute to why CLFS cannot complete the requested state transition.
What to inspect
- Determine the exact CLFS object being deleted: stream, physical log, or container.
- Close owner handles and archive contexts through supported APIs before retrying maintenance.
- Use RemoveLogContainer or CLFS deletion APIs instead of deleting container files directly.
References
- Microsoft: Common Log File System functions and operation groups
- Microsoft: AddLogContainer sizing and physical-log growth
- Microsoft: CLFS base log files, containers, dedicated and multiplexed logs
Looking for a different code? Search another status or error code.