Volume group “pve” has insufficient free space (solved) Reviewed by AL on . I wanted to backup my CT when I got this error message: [box type="error"]INFO: Starting Backup of VM 100 (openvz) INFO: CTID 100 exist mounted running INFO: st I wanted to backup my CT when I got this error message: [box type="error"]INFO: Starting Backup of VM 100 (openvz) INFO: CTID 100 exist mounted running INFO: st Rating: 0
You Are Here: Home » Tiny Post » Volume group “pve” has insufficient free space (solved)

Volume group “pve” has insufficient free space (solved)

I wanted to backup my CT when I got this error message:

INFO: Starting Backup of VM 100 (openvz)
INFO: CTID 100 exist mounted running INFO: status = running
INFO: backup mode: snapshot INFO: ionice priority: 7
INFO: creating lvm snapshot of /dev/mapper/pve-data (‘/dev/pve/vzsnap-proxmox-0′)
INFO: Volume group “pve” has insufficient free space (0 extents): 256 required.
ERROR: Backup of VM 100 failed – command ‘lvcreate –size 1024M –snapshot –name vzsnap-proxmox-0 /dev/pve/data’ failed: exit code 5

I am running the following version of proxmox

proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.1-111 (running kernel: 2.6.32-24-pve)
pve-manager: 3.1-14 (running version: 3.1-14/d914b943)
pve-kernel-2.6.32-24-pve: 2.6.32-111
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-7
qemu-server: 3.1-4
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-13
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

By reading the error message it says that there isn’t enough free space on the LVM group, let’s check available free space with the “vgdisplay” command

proxmox:~# vgdisplay
  --- Volume group ---
  VG Name               pve
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  7
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               203.03 GiB
  PE Size               4.00 MiB
  Total PE              51976
  Alloc PE / Size       49928 / 203.03 GiB
  Free  PE / Size       0 / 0 GiB
  VG UUID               EmHgKl-tB2B-zH4g-uAr9-51Ae-pjXE-f9VJAY

This is the procedure (or at least it worked for me):

Use at your own risk !!!

You need first to stop all your VM/CT and unmount the volume like this:

proxmox:~# /etc/init.d/vz stop    #it will stop all openvz servers
proxmox:~# umount /var/lib/vz

Checking the file system before we proceed

proxmox:~# e2fsck -f /dev/pve/data

Resizing the file system, in my case I chose to set it to 195

proxmox:~# resize2fs /dev/pve/data 195G

Now we are going to reduce the size of a logical volume

proxmox:~# lvreduce -L -8G /dev/pve/data

We check everything again

proxmox:~# vgdisplay
  --- Volume group ---
  VG Name               pve
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  7
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               203.03 GiB
  PE Size               4.00 MiB
  Total PE              51976
  Alloc PE / Size       49928 / 195.03 GiB
  Free  PE / Size       2048 / 8.00 GiB
  VG UUID               EmHgKl-tB2B-zH4g-uAr9-51Ae-pjXE-f9VJAY

Rechecking the file system
proxmox:~# e2fsck -f /dev/pve/data
Mounting the /var/lib/vz back
proxmox:~# mount /var/lib/vz
Checking file system disks
proxmox:~# df -h
Now we can test the backup if it works

proxmox:~# vzdump 200 --mode snapshot --compress gzip --dumpdir /data/backup_proxmox/

Hope this did help you solving your problem, let us know if it does and post your “pveversion -v” to let others know it. Thank you.

doge_icon
Clip to Evernote

About The Author

Network and system engineer

Number of Entries : 70
  • Aalex Gabi

    Thank you. You saved me of a lot of work. I got the same ‘pveversion -v’ as you. Everything seems to be working fine. Can you explain a little more what each command does? It was a little bit confusing for me.

    • http://terraltech.com AL

      I am glad that this post helped you out!
      for command details and explanation : (“man” is your friend)
      e2fsck – check a Linux ext2/ext3/ext4 file system
      pveversion – Print version information for Proxmox VE packages
      vgdisplay – display attributes of volume groups
      resize2fs – ext2/ext3/ext4 file system resizer
      lvreduce – reduce the size of a logical volume
      vzdump – backup utility for virtual machine

Scroll to top