| Previous | Next |
| STATUS_LOG_SECTOR_REMAPPED | STATUS_LOG_INVALID_RANGE |
STATUS_LOG_BLOCK_INCOMPLETE
STATUS_LOG_BLOCK_INCOMPLETE means CLFS reached a log I/O block that is partial rather than a complete block ready for record processing. A CLFS record is stored inside a log I/O block, so a partial block is not safely equivalent to a shorter application record.
This differs from STATUS_LOG_BLOCK_INVALID, where a complete block fails validation, and from STATUS_LOG_SECTOR_PARITY_INVALID, which identifies a sector parity failure. The status does not identify the event that made the block partial, so storage, crash, and restore evidence must be considered separately.
Diagnose the write boundary
- Identify the last LSN that the writer forced or flushed to stable storage, if application or CLFS diagnostics retain it.
- Preserve the entire base file and container sequence before retrying writes that could advance the active log.
- Use a CLFS-aware validation or restore process; do not treat the remaining bytes as an ordinary truncated document.
References
- Microsoft: CLFS stable storage
- Microsoft: CLFS flush and read functions
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.