| Previous | Next |
| STATUS_LOG_PINNED | STATUS_LOG_INCONSISTENT_SECURITY |
STATUS_LOG_METADATA_FLUSH_FAILED
STATUS_LOG_METADATA_FLUSH_FAILED concerns the durable metadata that describes the CLFS log and its state. A record path can involve client buffers, containers, LSNs, and metadata; a failure to flush metadata makes it unsafe to assume that a later open or recovery will observe the intended topology or state transition.
This differs from STATUS_LOG_CONTAINER_WRITE_FAILED, which reports a container write problem, and from STATUS_LOG_APPENDED_FLUSH_FAILED, which reports an append or reservation change that could not be flushed.
What to inspect
- Preserve the complete physical log and first storage error before retrying an operation that changes metadata again.
- Correlate the failure with container add/remove, policy, archive, tail, or other metadata-changing actions.
- Use documented validation and recovery procedures rather than editing base-log metadata by hand.
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.