...
If it should become necessary to expand the storage space for the partition at the /data mount point 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 mount point on mountpoint on an NMIS VM as this partition contains the following directories:
...
If the sudo lsblk command produces partition entries in the TYPE column of type lvm, then that partition is using LVM.In the example command below, using a recent release of the NMIS VM that does not use LVM, we have disks /dev/sda and /dev/sdb.
/dev/sda has partitions /dev/sda1 to /dev/sda4 and all partitions are TYPE part
/dev/sdb has partition /dev/sdb1 of TYPE part
| Code Block |
|---|
sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 120G 0 disk ├─sda1 8:1 0 1G 0 part /boot ├─sda2 8:2 0 15G 0 part / ├─sda3 8:3 0 1G 0 part [SWAP] └─sda4 8:4 0 103G 0 part /var sdb 8:16 0 120G 0 disk └─sdb1 8:17 0 120G 0 part /data |
In the example command below, using a recent release of the NMIS VM that does not use LVM, we have disks /dev/sda and /dev/sdb.
/dev/sda has partitions /dev/sda1 to /dev/sda4 and all partitions are TYPE part
/dev/sdb has partition /dev/sdb1 of TYPE part
If your NMIS VM is using partitions partition of type lvm lvm for partition at mountpoint /data, then proceed to the paragraph below NMIS VMs' using LVM
Otherwise, continue with the next paragraph NMIS VMs' using Traditional Disk Partitions
...
Grow the partition at the /data mount point mountpoint, which we now know from the df -h commands above is /dev/sdb1:
...