| Previous | Next |
| STATUS_CLUSTER_NODE_ALREADY_MEMBER | STATUS_NO_TXF_METADATA |
STATUS_COULD_NOT_RESIZE_LOG
The requested log resize could not be completed in the current state
Transaction logs cannot always be expanded or contracted immediately. Active transactions, recovery records, archive requirements, container layout, free space, and configured growth policy can all constrain the usable range of a durable log.
This warning is different from an invalid requested size: the value may be structurally acceptable, yet the log manager cannot reach it now. Query the resource-manager information before changing parameters so the current log range and state are known.
What to inspect
- Capture the requested minimum and maximum sizes and the current log information.
- Check free space, quotas, container files, and storage errors on the volume that holds the log.
- Look for long-running or in-doubt transactions that prevent truncation of active records.
- Avoid deleting log files or TxF metadata manually; that can destroy recovery information.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: FSCTL_TXFS_QUERY_RM_INFORMATION
- Microsoft: FSCTL_TXFS_MODIFY_RM
- Microsoft: using log streams with KTM
- Microsoft: alternatives to Transactional NTFS
Looking for a different code? Search another status or error code.