| Previous | Next |
| ERROR_LOG_CONTAINER_READ_FAILED | ERROR_LOG_CONTAINER_OPEN_FAILED |
ERROR_LOG_CONTAINER_WRITE_FAILED
Log service encountered an error when attempting to write to a log container.
ERROR_LOG_CONTAINER_WRITE_FAILED is Win32 error 6640 (0x000019F0) and concerns writing data to a CLFS log container.
Where the result appears
- appending a transaction record.
- writing a restart area.
- extending a log into a new container.
- persisting records before a dependent data-file update.
What to verify
Verify whether the selected container accepts the requested write and makes the expected bytes available to CLFS. Check container identity and write offset, record length and marshaling sizes, and free space, quota, and allocation status.
Likely causes
- the volume is full or quota constrained.
- the container became read-only or inaccessible.
- the storage stack rejected or partially completed the write.
- a handle or stream mapping became stale.
- file-system corruption prevents allocation or completion.
Troubleshooting steps
- Collect container identity and write offset.
- Record record length and marshaling sizes.
- Correlate free space, quota, and allocation status with the owning application log, CLFS-related System events, storage events, and any transaction or recovery trace.
Handling, retry, and recovery
Stop dependent commits, preserve the first I/O status, restore writable storage or capacity, and verify the log before resuming writers.
Related errors
ERROR_LOG_APPENDED_FLUSH_FAILED means records were appended but durability could not be confirmed; this code means the container write operation itself failed.
Example
A database appends a recovery record while the log volume is at quota. The append fails before the data page is changed; increasing the quota and verifying the container permits a safe retry.
References
Looking for a different code? Search another status or error code.
