Grow an LVM logical volume and XFS/ext4 filesystem online

Work in an authorized Bash shell on the host that owns this mount, not inside an unrelated container or rescue image with a different mount namespace. Record the installed kernel and package builds. lvm2 provides the LV commands, xfsprogs the XFS utilities, e2fsprogs the ext4 utilities, and util-linux/coreutils the mount/device inspection tools.

Use the selected distribution’s package query below. The command lookup runs with the same sudo environment used for privileged storage commands, so a missing root-only executable is not confused with a user PATH omission.

Use the official repositories for this Ubuntu or Debian release. Debian 12 is in LTS with architecture/package-specific coverage. Existing activation and AppArmor policy remain unchanged.

cat /etc/os-release
uname -r
bash --version
dpkg-query -W lvm2 xfsprogs e2fsprogs util-linux coreutils
sudo sh -c 'command -v lvs vgs lvextend vgcfgbackup xfs_growfs xfs_info resize2fs findmnt lsblk blockdev readlink awk sort tr mktemp tee'
sudo lvm version

Skip this panel when the tools already exist. Otherwise inspect and approve the package manager’s proposed transaction in a suitable maintenance window. Use only the active official repositories for this exact distribution/release. Installing packages can trigger package-owned hooks or units; do not treat it as a read-only incident diagnostic.

Do not start a new LVM daemon, activate another VG, change a devices file/filter or replace the existing activation/monitoring policy for this guide. The already active LV is a prerequisite. SELinux/AppArmor and device permissions remain enforced; solve a specific denial with the host owner instead of switching them off.

sudo apt-get update
sudo apt-get install lvm2 xfsprogs e2fsprogs util-linux coreutils
sudo sh -c 'command -v lvs vgs lvextend vgcfgbackup xfs_growfs resize2fs findmnt blockdev'

Inspect the exact mountpoint and follow its source through the block-device tree. The LV may appear under a mapper name while the form uses its VG/LV alias; these names must resolve to the same device. Read every LVM warning and stop for missing PVs, partial/inconsistent metadata or unhealthy storage before growing anything.

VG free space is space already assigned to physical volumes in this VG but not allocated to an LV. Filesystem free space is a different number. A larger provider disk or unused partition space does not appear as VG extents until a separate approved lower-layer change is complete. Do not use all free extents simply because they exist.

findmnt --mountpoint '/srv/data' -o TARGET,SOURCE,FSTYPE,FSROOT,OPTIONS
sudo lvs --segments -o lv_path,lv_attr,segtype,lv_size,vg_name,lv_health_status,devices '/dev/vg_data/lv_data'
sudo vgs -o vg_name,vg_attr,vg_size,vg_free,vg_extent_size,vg_free_count
lsblk -o NAME,TYPE,FSTYPE,SIZE,MOUNTPOINTS
df -hT -- '/srv/data'
df -i -- '/srv/data'

For XFS, inspect the current geometry and the no-change growfs check. Require an internal log and no separate realtime-device topology for this simple path. Stop for an external log or realtime device. The -n option does not grow anything; it checks arguments and prints geometry.

For ext4, read the existing superblock/features only. This is not an offline consistency check or full health certificate. Resolve metadata or I/O errors with the storage owner before growth. The panel selects one read-only branch from the mounted type; the next step still has to prove the exact LV-to-mount mapping.

fs=$(findmnt -rn --mountpoint '/srv/data' -o FSTYPE) || exit 1
case "$fs" in
    xfs) sudo xfs_info '/srv/data' || exit 1
         sudo xfs_growfs -n '/srv/data' || exit 1 ;;
    ext4) sudo dumpe2fs -h '/dev/vg_data/lv_data' || exit 1 ;;
    *) printf '%s\n' 'STOP: this guide requires XFS or ext4.'; exit 1 ;;
esac