To resolve this, increase the IMSVA partition, /dev/mapper/IMSVA-Spool. Note that this procedure is applicable for IMSVA installed on VMs. For the physical server, consult the server administrator.
- Check current disk usage. In this example, /dev/mapper/IMSVA-Spool will be increased.
Click image to enlarge.
- Add additional hard disk to your VM.
Click image to enlarge.
- Check if the disk has been recognized by the server. In the example below, 20GB on disk (/dev/sdb) has been added.
Click image to enlarge.
- Create a new partition.
Click image to enlarge.
- Check if the disk has been added.
Click image to enlarge.
- Reboot the server.
Click image to enlarge.
- Create physical volume.
Click image to enlarge.
- Run #pvscan or pvdisplay to verify the physical volume added.
Click image to enlarge.
- Check the VG size. In the example below, it’s currently 59.72GB.
Click image to enlarge.
- Extend “IMSVA” volume group by running “vgextend” command. In the example below, it is now 79.9 GB.
Click image to enlarge.
Click image to enlarge.
- Extend the logical partition by running the command below. Note that this may take a few minutes depending on the size of the disk space you added.
Click image to enlarge.
- Check the disk usage again by running df –h. in the example below, it is still the same as before. Run”resize2fs /dev/mapper/IMSVA-Spool”.
Click image to enlarge.
- Check IMSVA functionality and ensure everything works fine.