| Previous | Next |
| STATUS_LOG_BLOCK_VERSION | STATUS_LOG_READ_MODE_INVALID |
STATUS_LOG_BLOCK_INVALID
STATUS_LOG_BLOCK_INVALID means a CLFS log I/O block cannot be accepted as a valid block during log processing. CLFS records are marshalled into blocks and later read from sector-aligned blocks on stable storage, so this is not simply a validation failure for one application payload.
Use the adjacent statuses to narrow the stage: STATUS_LOG_BLOCK_INCOMPLETE identifies a partial block, STATUS_LOG_BLOCK_VERSION identifies a version issue, and STATUS_LOG_SECTOR_INVALID points to the sector level. This code does not name a particular root cause by itself.
Investigate the block as part of the log
- Capture the LSN, logical container identifier, block offset, and record sequence where diagnostics expose them.
- Validate the base file and all containers as one CLFS log rather than testing a copied container in isolation.
- Preserve a read-only recovery copy before any operation that changes the base LSN, archive tail, or container set.
References
- Microsoft: CLFS stable storage and LSN layout
- Microsoft: CLFS concepts
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.