It is possible to increase the size of the data LVM volume (where the logs are stored). There is a service that runs at boot (lvmresizer.service) which scans the disks and partitions; it then automatically adds new empty disks (and any un-partitioned space at the end of the used disks) to the data volume.
When rebooting an appliance this space gets added automatically to the data volume, however it can be done without rebooting by restarting the service:
systemctl restart lvmresizer.service
On some platforms, like VMWare ESXi, the kernel first needs to be explicitly notified of the changed disk size, like this:
echo 1 > /sys/class/block/sda/device/rescan
Replace sda with the device name.
Advanced disk resizing
This can be done by extending the size of the current disk used by the czvg LVM group. You can see what partition is being used running this command:
pvdisplay
Example:
--- Physical volume ---
PV Name /dev/nvme0n1p2
VG Name czvg
That means the the partition nvme0n1p2 is the one used by the czvg LVM group.
Once you have extended the disk size (modifying it in AWS or GCP console for instance) there are 2 ways to extend the size in the data LVM volume:
reboot the appliance and once it's online again you will have the new space in the data LVM volume.
run the command `systemctl start lvmresizer`. Once it's completed you will have the new space in the data LVM volume.
Example: An appliance in AWS with initially 20G of disk where we increased the disk to 40G using the AWS console
root@host:/home/cz# df -h|grep data
/dev/czvg/data 9.5G 98M 8.9G 2% /mnt/data
root@host:/home/cz# vgdisplay |grep "VG Size"
VG Size <19.75 GiB
root@host:/home/cz# fdisk -l /dev/nvme0n1|head -1
Disk /dev/nvme0n1: 40 GiB, 42949672960 bytes, 83886080 sectors
root@host:/home/cz# systemctl start lvmresizer.service
root@host:/home/cz# vgdisplay |grep "VG Size"
VG Size <39.75 GiB
root@host:/home/cz# df -h|grep data
/dev/czvg/data 30G 103M 28G 1% /mnt/data