| Previous | Next |
| ERROR_LOG_INCONSISTENT_SECURITY | ERROR_LOG_PINNED_RESERVATION |
ERROR_LOG_APPENDED_FLUSH_FAILED
Records were appended to the log or reservation changes were made, but the log could not be flushed.
ERROR_LOG_APPENDED_FLUSH_FAILED is Win32 error 6647 (0x000019F7) in Common Log File System (CLFS).
Where the result appears
- committing a transaction record.
- changing reserved log space.
- writing a checkpoint that must precede data changes.
- closing a client after appending recovery information.
What to verify
Verify whether the newly appended records or reservation update is confirmed durable before dependent work proceeds. Check LSN returned by the append, flush mode and completion status, and dependent data updates already issued.
Likely causes
- the append reached cache but the durability flush failed.
- the volume became unavailable after the write.
- storage reported a media or controller error.
- a failover interrupted the flush barrier.
- the application continued after a partial append path.
Troubleshooting steps
- Collect LSN returned by the append.
- Record flush mode and completion status.
- Correlate dependent data updates already issued with the owning application log, CLFS-related System events, storage events, and any transaction or recovery trace.
Handling, retry, and recovery
Assume commit state is uncertain, prevent dependent irreversible actions, reopen or verify the log, and use the application transaction protocol to decide whether to replay, compensate, or retry.
Related errors
ERROR_LOG_CONTAINER_WRITE_FAILED means the write failed; this code allows that bytes were appended but says durability was not established.
Example
A service receives an LSN for a commit record but the subsequent flush fails. It records the transaction as indeterminate and checks the log after storage recovery instead of issuing the business operation twice.
References
Looking for a different code? Search another status or error code.