| Previous | Next |
| STATUS_LOG_PINNED_ARCHIVE_TAIL | STATUS_LOG_RECORDS_RESERVED_INVALID |
STATUS_LOG_RECORD_NONEXISTENT
STATUS_LOG_RECORD_NONEXISTENT means the LSN supplied to CLFS does not identify a record in the log. An LSN carries a logical container identifier, block offset, and record sequence number, so a numerically well-formed LSN is not sufficient evidence that a record currently exists at that logical address.
This differs from STATUS_LOG_INVALID_RANGE, which describes an address outside the active range, and from STATUS_LOG_START_OF_LOG, which explicitly describes moving backward beyond the start. The correct response is to recover a valid scan or restart position, not to invent a nearby LSN.
Rebuild from valid log state
- Capture the requested LSN together with current base and last LSN metadata.
- Check whether container recycling, truncation, archive handling, or a stale caller checkpoint made the prior LSN no longer usable.
- Start a new CLFS read sequence from a documented valid boundary or from a validated restart point.
References
- Microsoft: CLFS stable storage and LSN components
- Microsoft: CLFS functions for reading log records
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.