Views:

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.

  1. Check current disk usage. In this example, /dev/mapper/IMSVA-Spool will be increased.

    IMSVA Spool

    Click image to enlarge.

  2. Add additional hard disk to your VM.

    Add hard disk

    Click image to enlarge.

  3. Check if the disk has been recognized by the server. In the example below, 20GB on disk (/dev/sdb) has been added.

    Verify

    Click image to enlarge.

  4. Create a new partition.

    Create new partition

    Click image to enlarge.

  5. Check if the disk has been added.

    Verify added disk

    Click image to enlarge.

  6. Reboot the server.

    Reboot server

    Click image to enlarge.

  7. Create physical volume.

    Create physical volume

    Click image to enlarge.

  8. Run #pvscan or pvdisplay to verify the physical volume added.

    Check physical volume

    Click image to enlarge.

  9. Check the VG size. In the example below, it’s currently 59.72GB.

    Check the VG size

    Click image to enlarge.

  10. Extend “IMSVA” volume group by running “vgextend” command. In the example below, it is now 79.9 GB.

    Extend IMSVA volume group

    Click image to enlarge.

    Extend IMSVA volume group

    Click image to enlarge.

  11. 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.

    Extend logical partition

    Click image to enlarge.

  12. 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”.

    Check disk usage

    Click image to enlarge.

  13. Check IMSVA functionality and ensure everything works fine.