| Previous | Next |
| ERROR_LOG_BLOCK_VERSION | ERROR_LOG_READ_MODE_INVALID |
ERROR_LOG_BLOCK_INVALID
A CLFS log block failed structural validation
CLFS stores client records inside log blocks managed through marshalling areas. The block carries CLFS structure used for physical placement and traversal; only after that layer is valid can ReadLogRecord expose a client data or restart record. This error therefore indicates a physical/log-service validation failure, not merely an unexpected record type returned to the application.
Collect the entire physical log set and the surrounding storage events. Compare whether the failure occurs while opening the log, reading a particular LSN, or validating an archive restore. The location matters: a single active-range block can affect replay from a checkpoint, while metadata problems have broader impact. Avoid repeatedly writing to a log that is being investigated, because CLFS can continue advancing and recycling containers. Quiesce the owner where practical, preserve the files, and follow the component-specific repair or recovery procedure.
What to inspect
- Record the failing operation and LSN, if the caller has one, before additional log activity changes the active range.
- Collect the base log and all container files as one set.
- Use ValidateLog for archive/restore validation scenarios and the owner recovery path for live logs.
References
- Microsoft: CreateLogMarshallingArea, block buffers, and marshalling contexts
- Microsoft: ReadLogRecord and CLFS read context modes
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
Looking for a different code? Search another status or error code.