| Previous | Next |
| STATUS_LOG_CONTAINER_READ_FAILED | STATUS_LOG_CONTAINER_OPEN_FAILED |
STATUS_LOG_CONTAINER_WRITE_FAILED
STATUS_LOG_CONTAINER_WRITE_FAILED places the failure at the CLFS container write. A successful in-memory append request does not establish durable completion until the relevant data and metadata can be written and, where required, flushed to stable storage.
The code is distinct from STATUS_LOG_APPENDED_FLUSH_FAILED: that later status explicitly says records or reservation changes were made but the flush failed. Here the container write itself did not complete successfully.
What to inspect
- Capture the requested operation, target container, LSN range, free space, and the underlying filesystem or storage error.
- Determine whether the caller can safely retry according to its own record-idempotency contract; CLFS status alone does not prove that no partial state reached media.
- Avoid manually deleting or replacing the container while any CLFS handles or recovery procedure still depend on the physical log.
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.