Introduction

It It is always advisable to make a backup of the target VM first, ensuring you can recover your original VM should things go wrong !If it should become necessary to expand the storage space for the partition at the /data mountpoint, the following set of instructions should help you to perform that change with minimal NMIS downtime.

Generally you should only be needing to resize the partiton at the  /data mountpoint on an NMIS VM as this partition contains the following directories:

• nmis9/
  • database/
  • var/
  • backups
• omk/
  • var/
• mongo/
  • ( mongo/ is the directory set as the storage.dbPath set in /etc/mongod.conf )

If it should become necessary to expand the storage space for the partition at the /data mountpoint, the following set of instructions should help you to perform that change with minimal NMIS downtime.

Determine whether the VMs' partitions are using Logical Volume Manager (LVM)

First, determine whether the NMIS VM is using LVM:

...

If your NMIS VM is using partition of type lvm for partition at mountpoint /data, then proceed to the paragraph below NMIS VMs' using Logical Voume Manager (LVM)
Otherwise, continue with the next paragraph NMIS VMs' using Traditional Disk Partitions

...

This should not be necessary with regards to the NMIS VM and requires more effort and skill to achieve.
Growpart would in most cases not be the desired tool for this job.
GParted would be a useful tool for achieving this:
https://gparted.org/display-doc.php%3Fname%3Dmoving-space-between-partitions

NMIS VMs' using Logical Voume Manager (LVM)

The resizing procedure is quite simple, for size increases at least. The two required steps are:

...