Logical Volume Management (LVM)

Logical Volume Management (LVM) is a system for managing disk storage on Linux that gives you incredible flexibility. Instead of being stuck with a fixed-size partition that you can never change without wiping the drive, LVM lets you treat physical hard drives (or partitions on them) as a big pool of storage. You can then carve virtual disks out of that pool, grow them, shrink them, or move them between physical drives, all while the system is still running.

Let's start with the basic building blocks. A Physical Volume (PV) is any storage device that LVM can use. This could be a whole hard drive (like /dev/sdb), a single partition (like /dev/sda3), or even a RAID array. You mark a drive as a PV using the pvcreate command. Think of PVs as individual bricks of storage.

Next, a Volume Group (VG) is a collection of one or more Physical Volumes. You create a VG with the vgcreate command. The VG is like a big bucket of combined storage. The total size of the VG is the sum of all the PVs you add to it. You can add more PVs to a VG later if you need more space.

Finally, a Logical Volume (LV) is a virtual partition that you carve out of a Volume Group. You create one with lvcreate. This is what you actually format with a filesystem (like ext4 or XFS) and mount to a directory so you can store files. An LV can be smaller than the total VG, and you can expand it later if you have free space in the VG.

Why does this matter? Imagine you have a server with a single 500GB hard drive. You partition it into a 200GB root partition (/) and a 300GB data partition (/data). Over time, the data partition fills up. Without LVM, you are in trouble. You would have to back up all the data, repartition the drive (which wipes everything), restore the data, and hope you guessed the new sizes correctly. This takes the server offline, costs hours of work, and risks data loss.

With LVM, you simply add a second 500GB hard drive to the server. You mark the new drive as a PV with pvcreate /dev/sdc. You add it to the existing VG with vgextend. Then you extend your Logical Volume with lvextend -L +500G /dev/vg_name/lv_data. Finally, you resize the filesystem with resize2fs (for ext4) or xfs_growfs (for XFS). The whole process takes minutes, does not require a reboot, and does not touch any existing data.

LVM also supports snapshots, which let you take a point-in-time copy of a Logical Volume without halting the system. This is brilliant for backups or testing changes before applying them permanently.

Key commands you must know for LFCS: - pvcreate / pvdisplay / pvs: manage Physical Volumes - vgcreate / vgdisplay / vgs / vgextend: manage Volume Groups - lvcreate / lvdisplay / lvs / lvextend / lvreduce: manage Logical Volumes - lvresize: can both extend and reduce LVs - resize2fs (ext4) or xfs_growfs (XFS): resize the filesystem inside the LV after you resize the LV itself

Remember: the order of resizing matters. First resize the LV, then resize the filesystem. For shrinking, you must defragment and resize the filesystem first, then shrink the LV. This is a common trap in the LFCS exam.

You are a junior Linux administrator at a mid-size e-commerce company. The company runs its online store on a single Linux server. The server has a 1TB hard drive split into three partitions: / (50GB), /var (200GB, where logs and databases live), and /data (750GB, where product images and customer uploads are stored). The /var partition is filling up fast because the database keeps growing. The server is critical, and downtime costs the company £10,000 per hour.

Without LVM, you would be panicking. With LVM, you have a plan. The server was set up with LVM during initial deployment, so all three partitions are Logical Volumes inside a single Volume Group called 'vg_store'. You check the Volume Group free space using the vgs command. You see there is 50GB free in the VG. You can immediately add that 50GB to the /var LV using lvextend -L +50G /dev/vg_store/var and then grow the filesystem with resize2fs /dev/vg_store/var. The server never goes offline, and the database keeps running the whole time.

A few months later, the company decides to add a new product feature that requires storing high-resolution videos. The /data partition is now 95% full, and the VG has no free space left. You have been authorised to buy a new 2TB hard drive. You install it in the server, run pvcreate /dev/sdb to make it a Physical Volume, then vgextend vg_store /dev/sdb to add the 2TB to your storage pool. Now you have plenty of free space. You extend the /data LV with lvextend -r /dev/vg_store/data -L +1.5T. The -r flag automatically resizes the filesystem as well.

In practice, an IT professional uses LVM for:

The key tools you use daily are: - lvs to check current Logical Volume sizes and names - vgs to see free space in your Volume Group - lvextend with -L (absolute size) or -l (in extents) to grow LVs - pvmove to relocate data from one failing drive to a healthy one

This flexibility is why nearly every production Linux server uses LVM. The LFCS exam tests your ability to read and understand command output, know the correct order of operations, and recognise the right commands for each task.