| Previous | Next |
| ERROR_LOG_RECORDS_RESERVED_INVALID | ERROR_LOG_TAIL_INVALID |
ERROR_LOG_SPACE_RESERVED_INVALID
The reserved log-space amount is inconsistent with current reservation state
CLFS can reserve log space before records are appended. Space reservation is measured separately from the number of reserved records, which is why Windows defines distinct errors for invalid record counts and invalid reserved space. The byte amount must remain consistent with the outstanding reservation and the record/block alignment overhead CLFS accounts for.
Capture the byte deltas passed to ReserveAndAppendLog and any alignment calculation used by the caller. If the application predicts record space itself, verify that it uses the CLFS reservation/alignment APIs rather than only summing payload lengths; log blocks and headers add storage overhead. Look for duplicate releases after asynchronous retries and for mixing reservation collections between streams. Enlarging the log does not repair invalid reservation arithmetic, although a separate log-full condition can exist at the same time.
What to inspect
- Compare requested reserved bytes with CLFS-aligned reservation calculations, not raw payload size alone.
- Trace each reservation adjustment through asynchronous completion and retry paths.
- Keep byte-space and record-count accounting separate in diagnostics.
References
- Microsoft: ReserveAndAppendLog reservation and append semantics
- Microsoft: Common Log File System functions and operation groups
- .NET LogRecordSequence over CLFS: reservations, base sequence, restart areas, and policies
Looking for a different code? Search another status or error code.