| Previous | Next |
| ERROR_LOG_APPENDED_FLUSH_FAILED | ERROR_INVALID_TRANSACTION |
ERROR_LOG_PINNED_RESERVATION
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.
ERROR_LOG_PINNED_RESERVATION is Win32 error 6648 (0x000019F8) and concerns CLFS log space pinned by outstanding reservations.
Where the result appears
- reserving space for a transaction.
- handling a nearly full log.
- shrinking or recycling containers.
- recovering after clients reserved more space than they consumed.
What to verify
Verify whether reserved log capacity leaves enough reclaimable space for the requested append or growth operation. Check reservation amount per client, used versus reserved bytes, and oldest reservation LSN.
Likely causes
- clients hold reservations that cover most of the log.
- aborted operations did not free reservations.
- reservation estimates are much larger than actual records.
- a stale client context survived longer than intended.
- reclamation cannot pass the oldest reserved range.
Troubleshooting steps
- Collect reservation amount per client.
- Record used versus reserved bytes.
- Correlate oldest reservation LSN with the owning application log, CLFS-related System events, storage events, and any transaction or recovery trace.
Handling, retry, and recovery
Free reservations for completed or abandoned operations, close stale clients, correct reservation sizing, and verify available space before allowing new high-volume transactions.
Related errors
ERROR_LOG_PINNED can be caused by restart or archive requirements; this code specifically points to reservation consumption.
Example
A batch importer reserves worst-case space for thousands of transactions and then aborts without releasing it. Closing the abandoned client context frees the reservations and lets CLFS recycle containers.
References
Looking for a different code? Search another status or error code.