Updated: 28 September 2026 · Applies to: LVM 2.03 on AlmaLinux and Rocky Linux 9 and 10, RHEL 9 and 10, Ubuntu 24.04 and 26.04, Debian 13

If a logical volume has a classic LVM snapshot, lvextend on it fails with:

Snapshot origin volumes can be resized only while inactive: try lvchange -an.

This message comes from LVM itself: a volume that is the origin of a (thick) snapshot can only be grown while it and its snapshots are deactivated, and it can never be shrunk. You have three ways forward.

Option 1: remove the snapshot if you no longer need it

Snapshots are usually temporary, for example taken before an update. If the update went well:

lvs -o lv_name,origin,snap_percent vgdata    # find the snapshot of the volume
lvremove vgdata/data_snap
lvextend -r -L +20G vgdata/data

-r grows the file system as well. To go back to the snapshot's state instead, merge it into the origin with lvconvert --merge vgdata/data_snap (the merge completes the next time the origin is activated, often at the next reboot for a mounted volume).

Option 2: grow it while deactivated

This keeps the snapshot but needs downtime:

  1. Stop what uses the volume and unmount it: umount /data
  2. Deactivate the origin (its snapshots are deactivated with it):
    lvchange -an vgdata/data
  3. Grow it and activate it again:
    lvextend -L +20G vgdata/data
    lvchange -ay vgdata/data
  4. Grow the file system: mount it and run xfs_growfs /data (XFS) or resize2fs /dev/vgdata/data (ext4).

A snapshot also needs enough space for all blocks that change afterwards. Check its fill level with lvs (column Data% or Snap%); a full snapshot becomes invalid.

Option 3: use thin provisioning for future snapshots

Volumes in a thin pool can be resized while their thin snapshots exist, and snapshots are cheaper. If you take snapshots regularly, consider moving the data to a thin pool (lvcreate --type thin-pool, then thin volumes and lvcreate -s without a size).

Official documentation: lvmthin manual page and lvextend manual page.

Ucartz services for this topic

Was this answer helpful? 0 Users Found This Useful (0 Votes)