| Previous | Next |
| STATUS_LOG_SPACE_RESERVED_INVALID | STATUS_LOG_FULL |
STATUS_LOG_TAIL_INVALID
STATUS_LOG_TAIL_INVALID means CLFS rejected a new or existing archive tail, or the base of the active log. These are retention boundaries, not interchangeable offsets: a non-ephemeral log uses the archive tail to mark the last archived LSN, while restart-area processing can advance the base LSN for the active portion of a stream.
This differs from STATUS_LOG_PINNED_ARCHIVE_TAIL, where a valid tail still retains data and blocks recycling. Here the proposed or observed tail itself is invalid. It also differs from STATUS_LOG_START_OF_LOG, which reports a scan or write crossing the current start boundary.
Advance only from validated LSNs
- Record whether the operation is changing an archive tail or an active-log base, along with the current LSN boundaries.
- For archive-tail changes, confirm that the extent has actually been archived before advancing retention.
- For base-LSN changes, use a valid client restart point and verify that no recovery reader still requires the data being made recyclable.
References
- Microsoft: CLFS archive tail and restore workflow
- Microsoft: CLFS restart areas and active LSNs
- Microsoft: CLFS stable storage and logical containers
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.