| Previous | Next |
| STATUS_LOG_RESERVATION_INVALID | STATUS_LOG_CONTAINER_LIMIT_EXCEEDED |
STATUS_LOG_CANT_DELETE
STATUS_LOG_CANT_DELETE means that CLFS cannot delete a log file or file-system container at the time of the request. Deletion of a CLFS log is not necessarily immediate: the API marks a log for deletion, while actual deletion waits for log handles, marshalling areas, and read contexts to be closed.
The status does not identify which lifetime condition prevented deletion. It should not be reduced to a generic filesystem-access error, and it does not mean that removing a container directly is safe while the log remains active.
Close CLFS ownership deliberately
- Inventory every process and component holding the log, its marshalling areas, or read contexts.
- Finish or terminate active read sequences before retrying deletion.
- If the log is part of an archive or recovery workflow, preserve the complete set first and use the documented CLFS deletion or container-management operation.
References
- Microsoft: CLFS API reference and DeleteLogFile behavior
- Microsoft: creating and managing CLFS containers
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.