| Previous | Next |
| STATUS_BACKUP_CONTROLLER | STATUS_TOO_LATE |
STATUS_LOG_FILE_FULL
The operation cannot obtain the log space it needs
STATUS_LOG_FILE_FULL reports exhaustion of usable log space, which is not necessarily the same as a full data volume. Log-based components can require reserved space so that recovery, rollback or metadata updates can be recorded even when normal work is under pressure.
The NTSTATUS alone does not identify the logging provider. In a Common Log File System (CLFS) client, for example, Windows exposes reservation APIs and documents reservation as a way for transactional clients to avoid encountering log-full failures at inconvenient points. Other file-system or database-style components can have their own log lifecycle. Identify the provider before applying provider-specific cleanup.
Do not simply delete an active log file. Determine the log's retention, restart or truncation point and which clients still depend on older records. Removing log containers can turn a recoverable capacity problem into metadata loss.
What to inspect
- The component that returned the status and the physical or logical log it owns.
- Current log size, free/reserved space, archive or truncation progress, and oldest required record.
- Whether a stalled consumer, checkpoint or transaction is preventing log advancement.
References
- Microsoft: Common Log File System
- Microsoft: Appending records to a CLFS log
- Microsoft: ClfsReserveAndAppendLog
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.