| Previous | Next |
| STATUS_LOG_RECORD_NONEXISTENT | STATUS_LOG_SPACE_RESERVED_INVALID |
STATUS_LOG_RECORDS_RESERVED_INVALID
STATUS_LOG_RECORDS_RESERVED_INVALID focuses on the count of reserved records, or an adjustment to that count, in a CLFS marshalling area. The reservation interface accepts a count and an array of sizes; its behavior changes depending on whether the caller is only reserving, appending without a reservation, or appending by using existing reserved space.
The important distinction from STATUS_LOG_SPACE_RESERVED_INVALID is count versus byte-space accounting. It also differs from STATUS_LOG_RESERVATION_INVALID, which is the broader error for an invalid reservation allocation or release.
Check count, flags, and array shape together
- Record the reserve-record count, the length of the reservation-size array, and the flags used for the same call.
- Do not pass a reserve count when the API mode requires the array to be absent, such as using existing reservations.
- Keep reservation adjustments scoped to the marshalling area that owns them.
References
- Microsoft: ReserveAndAppendLog parameters and modes
- Microsoft: CLFS API reference
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.