If it should become necessary to expand the storage space for /data, the following set of instructions should help you to perform that change with minimal NMIS downtime.
The resizing procedure is quite simple, for size increases at least. The two required steps are:
- adding extra storage 'hardware' to the VM
- informing the operating system of the extra storage, attaching the storage and resizing the active file syst
First Step, determine the current state
login as as root to the VM and run
pvs
which will show you something like this
/dev/sdb vg_nmis64_data lvm2 a- 100.00g 0
meaning 100gb are allocated and vg_nmis64_data is using it. Note that on some older VMs the volume group is called vg_data instead; the resizing process can be performed as long as you remember to change the volume group name in the command invocations.
Next run
lvs
and it'll tell you
lv_data vg_nmis64_data -wi-ao 100.00g
that the lv_data logical volume is using all of vg_nmis64_data's space, and a final
df -h
will tell you that
/dev/mapper/vg_nmis64_data-lv_data 99G 39G 56G 42% /data
/data is the filesystem on top of the logical volume, which has a size of 99GB (plus spare change), of which 39BG are used. It is recommended that you rerun these commands at the end to verify that the resizing has worked.
Second Step, Resize Storage Hardware
At this point it'll be simplest to open your vmware client, resize the VM's disk 2 to the desired new size and then reboot the VM to make it pick up the size change.
Please note that vmware doesn't let you resize disks if there are any snapshots present; if that is the case, then these snapshots must be removed before the resize can occur.
Third Step, Informing the OS and resizing the file system
When the VM boots the newly resized disk 2 aka /dev/sdb will be detected but volume group and logical volume still need to be told about the change of 'hardware'.
Login as root, then run
pvresize /dev/sdb
which will tell you that sdb is now as large as the disk2 size you gave in vmware.
Now run
lvextend -l 100%VG /dev/vg_nmis64_data/lv_data
to perform the resizing for the logical volume, follwed by
resize2fs /dev/vg_nmis64_data/lv_data
which will take a bit of time and eventuallly tell you that it has resized the file system for the new extended disk size. A final
df -h
should show that /data is now larger than before.