| Previous | Next |
| STATUS_LOG_CONTAINER_STATE_INVALID | STATUS_LOG_PINNED |
STATUS_LOG_STATE_INVALID
STATUS_LOG_STATE_INVALID applies at log scope rather than to one container. The object may be present and readable enough for some calls, but its aggregate lifecycle state does not satisfy the precondition for the requested action.
The status is intentionally broader than STATUS_LOG_CONTAINER_STATE_INVALID. Diagnose the log type, archive state, client registration, open handles, and operation ordering before changing raw files or rebuilding a container inventory.
What to inspect
- Identify whether the handle represents a stream, a dedicated physical log, or a multiplexed physical log.
- Query current log information and correlate it with in-flight archive, management, container, and shutdown operations.
- Compare the API precondition with the observed state instead of treating a state mismatch as a transient I/O error.
References
- Microsoft: CLFS architecture, dedicated and multiplexed logs
- Microsoft: base log, containers, streams, and creation model
- Microsoft: CLFS user-mode API reference
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.