| Previous | Next |
| ERROR_LOG_FULL | ERROR_LOG_MULTIPLEXED |
ERROR_COULD_NOT_RESIZE_LOG
The log could not be set to the requested size.
ERROR_COULD_NOT_RESIZE_LOG is Win32 error 6629 (0x000019E5) and concerns a Common Log File System log resize request.
Where the result appears
- changing the size of a dedicated or multiplexed CLFS log.
- adding or removing containers while clients still hold log handles.
- applying a growth policy after a log-full notification.
- restoring a log whose container geometry differs from the requested size.
What to verify
Verify whether the requested physical log size can be represented by the current container layout and log policy. Check current and requested log sizes, container count, container sizes, and container paths, and restart-area and base-log metadata.
Likely causes
- the requested size is below the minimum required by metadata and active restart areas.
- container increments or alignment rules cannot produce the exact requested size.
- active clients, reservations, or pinned records prevent container removal.
- the volume lacks free space for the requested growth.
- another management operation changed the log between inspection and resize.
Troubleshooting steps
- Collect current and requested log sizes.
- Record container count, container sizes, and container paths.
- Correlate restart-area and base-log metadata with the owning application log, CLFS-related System events, storage events, and any transaction or recovery trace.
Handling, retry, and recovery
Recalculate a supported size from current CLFS metadata, release unnecessary reservations, archive or advance the base log, and repeat the resize only after the blocking state changes.
Related errors
ERROR_LOG_PINNED means reclamation is blocked by active records; this code instead reports that the requested resize itself could not be established.
Example
An administrator requests a smaller log while an application still pins records needed for recovery. Inspecting reservations and the base log shows that removing a container would discard required ranges, so the resize is deferred until the client advances its base sequence number.
References
Looking for a different code? Search another status or error code.