| Previous | Next |
| STATUS_LOG_CONTAINER_OPEN_FAILED | STATUS_LOG_STATE_INVALID |
STATUS_LOG_CONTAINER_STATE_INVALID
STATUS_LOG_CONTAINER_STATE_INVALID says that CLFS reached a container whose current state is incompatible with the requested action. It is more specific than a missing container and narrower than an invalid physical-log state: the decision concerns the selected container within the log topology.
Useful evidence is the intended operation and the container’s role in the active physical log. An attempted removal, recycle, archive, or write can have different preconditions, so the code should not be reduced to a generic disk-health conclusion.
What to inspect
- Record the container identifier, path, requested action, and current physical-log information before retrying.
- Use CLFS enumeration and information APIs to inspect the current container inventory rather than inferring state from filenames.
- Check whether an archive, tail, pin, or concurrent management action makes the requested container transition invalid at this time.
References
- Microsoft: physical CLFS log and container creation
- Microsoft: ScanLogContainers, GetLogContainerName, AddLogContainer, and RemoveLogContainer
- Microsoft Open Specifications: NTSTATUS values
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.