What happens when a disk gets full
The queue manager logging component can cope with a full disk, and with full log files. If the disk containing the log fills, the queue manager issues message AMQ6709 and an error record is taken.
The log files are created at their fixed size, rather than being extended as log records are written to them. This means that IBM MQ can run out of disk space only when it is creating a new file; it cannot run out of space when it is writing a record to the log. IBM MQ always knows how much space is available in the existing log files, and manages the space within the files accordingly.
From IBM MQ Version 9.1.0, when we use linear logging, you have the option to use:
- Automatic management of log extents.
See DISPLAY QMSTATUS for more information on the new log attributes.
Also, see the following commands, or their PCF equivalents:
- RESET QMGR
- SET LOG for distributed platforms
- The options controlling the use of media images.See the ALTER QMGR command and ALTER QUEUES for more information on:
- IMGINTVL
- IMGLOGLN
- IMGRCOVO
- IMGRCOVQ
- IMGSCHED
Circular logging returns a resource problem.
If you still run out of space, check that the configuration of the log in the queue manager configuration file is correct. We might be able to reduce the number of primary or secondary log files so that the log does not outgrow the available space.
We cannot alter the size of the log files for an existing queue manager. The queue manager requires that all log extents are the same size.
Parent topic: Manage logs