In some situations it may be necessary to increase the amount of disk space allocated to a Messaging Gateway (SMG) virtual machine to accommodate increased log or quarantine storage requirements. Prior to SMG 10.8.0 it was not possible to expand the SMG filesystem even though the underlying virtual disk had been expanded. This has been addressed with the 10.8.0 and later releases.
Modification of the disk on an installed Messaging Gateway system carries with it some risk of filesystem corruption, loss of data, or in extreme cases loss of function of the SMG instance. Additionally, attempting to expand the disk space on SMG systems originally installed with a version prior to 10.6.0 will either result in the system becoming unstable and loss of all data (10.8.0) or in a warning that the filesystem cannot be safely expanded (10.8.1 and later).
It is highly recommended that both a virtual machine snapshot be taken before modifying the SMG system and also a full backup be collected if the SMG system is a Control Center host.
The grow-disk command will issue a warning if the underlying disk subsystem is incompatible and cannot be expanded:
smg [10.8.1-2]> grow-disk --status
Incompatible file system found.
grow-disk can only be run on a system originally installed with SMG 10.6.0 or later.
Release : 10.8.0
To expand the disk space available to SMG for virtual machines under VMWare, Hyper-V, and Linux KVM:
usage: grow-disk [ --resize | --status ]
Just perform the final resize of the filesystem
Will perform a reboot
Show the characteristics of the physical disk and partitions,
but make no changes
If no option is provided, the system will be rebooted, and the disk
partition table will be modified to increase the size of the /data
partition to the maximum space available.