| Previous | Next |
| STATUS_LOG_APPENDED_FLUSH_FAILED | STATUS_VIDEO_HUNG_DISPLAY_DRIVER_THREAD |
STATUS_LOG_PINNED_RESERVATION
STATUS_LOG_PINNED_RESERVATION identifies a specific form of log pinning: reserved records are consuming most of the available space. CLFS reservation APIs allocate sector-aligned capacity for future records, so an application can block later allocation even when it has not yet written an equivalent amount of record data.
This differs from a general STATUS_LOG_PINNED condition. The remediation target is the reservation lifecycle: determine which client holds the reservation and whether it must append, free, or re-size it under the documented contract.
What to inspect
- Measure outstanding reservations by client and correlate them with the operations that allocated but did not consume reserved log space.
- Free or complete reservations through CLFS APIs when the owning client no longer needs them; do not attempt to reclaim the corresponding space by removing containers.
- Review reservation sizing and concurrency assumptions so recovery paths cannot retain large reservations indefinitely.
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.