| Previous | Next |
| hrMissingLogFile | hrBadLogSignature |
hrLogDiskFull
What this return value changes
hrLogDiskFull means the volume hosting transaction logs cannot allocate the next required log write or generation.
The stored value is 0xC8000211 (negative JET error -529; -529). Current ESE documentation uses JET_errLogDiskFull for the corresponding published JET condition.
The first useful distinction is that free space on the database volume is irrelevant if logs are on a different volume. Start by capturing free and reserved space, log growth rate, checkpoint lag, circular-log policy, outstanding backup, and volume quotas.
Objects and state involved
| Diagnostic layer | durable write-ahead-log I/O and capacity of the log volume |
|---|---|
| Relevant API surface | transaction commit, log flush, generation creation, recovery undo, and backup truncation |
| Code-specific condition | the volume hosting transaction logs cannot allocate the next required log write or generation |
| Narrow corrective direction | create safe capacity on the log volume and let the owning service recover; never delete required logs ad hoc |
ESE must log changes before corresponding database pages become durable. Log storage is often separate from database storage and must be diagnosed independently.
Evidence worth preserving
- Code-specific observation: capture free and reserved space, log growth rate, checkpoint lag, circular-log policy, outstanding backup, and volume quotas.
How to distinguish nearby results
It specifically means that free space on the database volume is irrelevant if logs are on a different volume. Related values below can appear in the same workflow but require a different response:
hrLogWriteFail | the write-ahead log could not durably accept a required record |
|---|---|
hrNyi | the selected legacy Directory Service backup or restore entry point is present but that operation is not implemented |
hrConsistentTimeMismatch | the database last-consistent timestamp does not match the recovery or backup lineage being applied |
A safe response sequence
- Record it,
0xC8000211, the API name, the current phase, and all live context or file owners. - Verify the condition by capturing free and reserved space, log growth rate, checkpoint lag, circular-log policy, outstanding backup, and volume quotas.
- Apply only the targeted fix: create safe capacity on the log volume and let the owning service recover; never delete required logs ad hoc.
Actions that can make diagnosis worse
- Do not delete required log generations to free space.
- Do not keep accepting writes after durable logging has failed.
Technical references
- ESE log files and reserves — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- Transaction-log parameters
- ESE error codes
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.