| Previous | Next |
| ERROR_LOG_METADATA_INCONSISTENT | ERROR_LOG_CANT_DELETE |
ERROR_LOG_RESERVATION_INVALID
The log reservation operation is internally inconsistent
CLFS allows clients to reserve space before appending records. ReserveAndAppendLog can adjust reservations and append atomically, while higher-level LogRecordSequence exposes reservation collections. Reservations are bookkeeping against future log-space consumption; they are not the same as adding containers or moving the base LSN. An invalid reservation request means the allocation or release adjustment does not match the reservation state CLFS is tracking.
Trace reservation deltas in the exact order submitted by the client and associate them with the same marshalling area or reservation collection. Look for releasing space that was never reserved, applying a reservation object to another stream, integer conversion errors in byte counts, and retry logic that repeats an already completed adjustment. Do not solve this by enlarging the physical log: ERROR_LOG_RESERVATION_INVALID is about reservation accounting, whereas ERROR_LOG_FULL is about available log space.
What to inspect
- Log each reservation increment and decrement with stream identity and operation completion status.
- Check retry paths for duplicate release or duplicate reservation adjustments.
- Keep reservation state scoped to the CLFS stream and context that created it.
References
- Microsoft: ReserveAndAppendLog reservation and append semantics
- .NET LogRecordSequence over CLFS: reservations, base sequence, restart areas, and policies
- Microsoft: CreateLogMarshallingArea, block buffers, and marshalling contexts
Looking for a different code? Search another status or error code.