| Previous | Next |
| ERROR_LOG_POLICY_CONFLICT | ERROR_LOG_RECORD_NONEXISTENT |
ERROR_LOG_PINNED_ARCHIVE_TAIL
The archive tail is pinning reclaimable CLFS space
For a non-ephemeral archivable log, the archive tail records the last archived physical LSN. CLFS archive documentation explains that persistent log data must be archived periodically to reclaim space. SetLogArchiveTail advances that physical LSN after archival, and PrepareLogArchive reports the current archive tail and active-log extents. If the archive tail remains behind, containers holding unarchived extents cannot be recycled.
Inspect the archive workflow, not only current disk free space. Determine the last successful PrepareLogArchive/extent copy/SetLogArchiveTail sequence and check for archive contexts that were not terminated; Microsoft notes that outstanding archive contexts can defer archive-tail changes. Verify the new tail is a valid physical LSN from the same log. Do not advance the tail past data that has not been durably archived merely to clear the error, because that changes the retention guarantee the archive tail represents.
What to inspect
- Compare current archive tail, base LSN, and last valid LSN reported for the physical log.
- Check for incomplete archive contexts and failures before SetLogArchiveTail.
- Advance the archive tail only after the corresponding extents and metadata are durably archived.
References
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
- Microsoft: PrepareLogArchive and active-log extent snapshots
- Microsoft: SetLogArchiveTail and physical archive-tail LSN requirements
Looking for a different code? Search another status or error code.