| Previous | Next |
| STATUS_LOG_STATE_INVALID | STATUS_LOG_METADATA_FLUSH_FAILED |
STATUS_LOG_PINNED
STATUS_LOG_PINNED explains why the physical log cannot recycle space even when old records appear expendable to an application. A stream can pin its tail, and in a multiplexed log one stream that does not advance its tail can eventually prevent containers from being recycled for all streams.
This is not a reason to force deletion. A pin represents an active retention requirement such as unarchived history, a client tail, or another protected extent. The recovery path is to identify that requirement, not to bypass it with raw container changes.
What to inspect
- Collect base, tail, and archive-tail LSNs for every relevant stream and identify the client responsible for the oldest retained extent.
- Determine whether archive completion, a managed-client tail callback, or an application recovery obligation must occur before reclamation.
- Differentiate a generic pin from
STATUS_LOG_PINNED_RESERVATION, which specifically attributes pressure to reserved records.
References
- Microsoft: ClfsMgmtHandleLogFileFull and full-log handling
- Microsoft: CLFS containers, tail pinning, and managed clients
- Microsoft: container, reservation, append, and flush APIs
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.