| Previous | Next |
| STATUS_LOG_CONTAINER_WRITE_FAILED | STATUS_LOG_CONTAINER_STATE_INVALID |
STATUS_LOG_CONTAINER_OPEN_FAILED
STATUS_LOG_CONTAINER_OPEN_FAILED occurs before CLFS can perform an operation that needs a particular container. It can reflect a missing path, sharing or access restrictions, an unavailable storage target, or a container that cannot be opened as part of this physical log.
It is not equivalent to a corrupt block. First establish whether CLFS can locate and open the expected container set, then use structural-validation results to decide whether the data itself is valid.
What to inspect
- Enumerate the container names from the physical log and compare them with the paths actually available to the process.
- Check access and sharing state for the base log and containers as one set, including the account context that created containers.
- Preserve the first underlying open failure; later retries can replace a useful path or sharing error with a generic lifecycle result.
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.