| Previous | Next |
| ERROR_TRANSACTIONAL_OPEN_NOT_ALLOWED | ERROR_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE |
ERROR_LOG_GROWTH_FAILED
The RM log could not create additional space for transactional state
ERROR_LOG_GROWTH_FAILED belongs to the Windows Kernel Transaction Manager transaction-processing model. A transactional RM depends on durable log space for recovery data and outstanding transaction state. TxF resource managers expose log growth, extent, and sizing controls through `fsutil resource`, while custom KTM RMs can use CLFS log streams. Failure to grow the log can stop new transactional work even when ordinary file creation elsewhere on the volume still succeeds.
Inspect the event log entry recorded with the failure, current RM log policy, container count or size, and underlying free space and storage errors. Also check whether pinned or in-doubt transactions prevent reclaiming old log state. Increasing a generic application timeout will not create log capacity. For TxF, use supported resource-manager log controls; for a custom RM, diagnose its CLFS growth and archive or base-advance behavior rather than manipulating container files.
What to inspect
- Find the detailed event logged by the transactional resource manager.
- Measure RM log size, growth policy, free space, and unresolved transaction pressure.
- Use supported RM or CLFS log-management interfaces rather than deleting log containers.
References
- Microsoft: transactional resource manager and log management
- Microsoft: KTM resource-manager log streams and recovery
- Microsoft: KTM recovery processing and presumed abort
Looking for a different code? Search another status or error code.