| Previous | Next |
| STATUS_CURRENT_TRANSACTION_NOT_VALID | STATUS_OBJECT_NO_LONGER_EXISTS |
STATUS_LOG_GROWTH_FAILED
The log reached a point where it needed to grow and could not
A durable transaction log must retain records needed by active and recoverable transactions. When reusable space is exhausted, the resource manager may need another container or a larger configured range. Growth can fail because of disk space, quota, container creation, permissions, policy limits, or storage I/O errors.
The first failure is normally more useful than later transaction errors. The built-in description explicitly points to the event log, where the resource manager or storage stack may record the underlying cause.
What to inspect
- Collect the relevant event records, current RM log information, free space, quotas, and container paths.
- Find long-running or in-doubt transactions that keep the log tail from advancing.
- Check whether automatic growth is enabled and whether configured limits were reached.
- Do not simply enlarge the log without addressing transactions or storage faults that prevent reuse.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: using log streams with KTM
- Microsoft: FSCTL_TXFS_QUERY_RM_INFORMATION
- Microsoft: FSCTL_TXFS_MODIFY_RM
Looking for a different code? Search another status or error code.