| Previous | Next |
| STATUS_LOG_POLICY_CONFLICT | STATUS_LOG_RECORD_NONEXISTENT |
STATUS_LOG_PINNED_ARCHIVE_TAIL
STATUS_LOG_PINNED_ARCHIVE_TAIL explains why CLFS cannot reclaim log space: the archive tail still pins the retained history. For a non-ephemeral log, CLFS tracks the last archived LSN as the archive tail; only after archive processing and a valid tail advance can older data become eligible for recycling.
This is not a generic disk-full message and it is not a reason to move the tail speculatively. A base LSN and archive tail serve different retention purposes. Advancing the archive tail before the corresponding data is safely archived defeats the retention model that is causing the pin.
Archive first, then reclaim
- Determine whether the log is archivable or ephemeral and identify the current archive-tail LSN.
- Prepare and complete archive handling for the required log extent before setting a newer archive tail.
- If history must remain available, add capacity or restore a valid archive workflow instead of discarding pinned data.
References
- Microsoft: CLFS archive and restore model
- Microsoft: CLFS concepts and archive tails
- Microsoft: ReserveAndAppendLog and full-log remedies
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.