It is common for a virtualized Guest OS base image to have a generic minimal storage capacity. But this capacity can easily be exceeded by production scenarios, performance testing, logging, or even the general cruft of running a machine 24×7.
For this reason, extending a virtualized disk can be extremely helpful. Here is a walk through for extending a disk using fdisk on an Ubuntu system that is using classic partitions. For performing this operation with LVM enabled, see my post here.
This type of change is typically made with a live CD to ensure exclusive disk access and gparted GUI for convenience. But we will use fdisk here so that it could be done from a remote terminal or by automation.
Continue reading “Ubuntu: Extending a virtualized disk using fdisk when not using LVM”
Before virtualization, there was a stronger argument for using a swap partition instead of a swap file for servers. A fragmented swap file could lead to performance issues that a statically sized and placed partition did not have consider.
But once virtualization comes into play, unless you go to great lengths to segment your storage pools, that swap partition is not guaranteed to be either statically sized or statically placed on a physical platter. And at that point, you should consider using a swap file which provides more flexibility in sizing and capacity planning.
Here are instructions for adding a 16Gb swap file to Ubuntu:
Continue reading “Ubuntu: Using a swap file instead of swap partition for virtualized server VMs”