Insufficient free extents (0) in volume group pve: 256 required: can't solve this ?

askmurphy

Renowned Member
Nov 12, 2011
3
0
66
Hello !
I have a server running proxmox 1.9 , I want to backup the snapshot's to an NFS, but I get this error:

VMID
NAME
STATUS
TIME
SIZE
FILENAME
101
--ftdn--
FAILED
00:00:01
00:00:02
0KB

[TD="colspan: 2"]command 'lvcreate --size 1024M --snapshot --name 'vzsnap-as213524.domain.com-0' '/dev/pve/data'' failed with exit code 5
[/TD]

[TD="colspan: 3"]TOTAL
[/TD]



...
Detailed backup logs:
...

vzdump --quiet --snapshot --compress --storage backup --maxfiles 10 --mailto my@email.com 101

101: nov 12 19:00:02 INFO: Starting Backup of VM 101 (qemu)
101: nov 12 19:00:02 INFO: running
101: nov 12 19:00:02 INFO: status = running
101: nov 12 19:00:02 INFO: backup mode: snapshot
101: nov 12 19:00:02 INFO: ionice priority: 7
101: nov 12 19:00:02 INFO: Insufficient free extents (0) in volume group pve: 256 required
101: nov 12 19:00:02 ERROR: Backup of VM 101 failed - command 'lvcreate --size 1024M --snapshot --name 'vzsnap-as213524.domain.com-0' '/dev/pve/data'' failed with exit code 5

vgdisplay gives this:

--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
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 1,80 TB
PE Size 4,00 MB
Total PE 471675
Alloc PE / Size 471675 / 1,80 TB
Free PE / Size 0 / 0
VG UUID NSjJ0B-uUtI-2T0V-YAcl-dC03-PKj3-0RwcJV

pvdisplay gives this:

--- Physical volume ---
PV Name /dev/sda5
VG Name pve
PV Size 1,80 TB / not usable 1023,50 KB
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 471675
Free PE 0
Allocated PE 471675
PV UUID 7BCYfp-S9nS-VoP0-Io0r-C6wz-iAfX-BTR968

I have tried a few things, but I can't fix it...
I am desperate !
I hope somebody can help ?
Many thanks in advance !
 
Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this

Hi,
on a standard-installation you have 4GB free space on the pve-vg for backup (snapshot).
Your trouble can have some possible causes:
1. your backup-volume is on the same vg (e.g. backup to the root-filesystem).
2. your snapshot are to big - or an second snapshot exist.
3. you use the full space of the vg for your filesystems (data, root, swap...)

Look with lvdisplay for snapshots.

Udo
 
Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this

Hi,

It seems that there is no free space to do a snapshot :
Code:
Free  PE / Size       0 / 0

I would bet that it is not a standard proxmox-ve installation (with the CD), but an installation on top of squeeze, and that letting some space in the VG for this has been forgotten.

You have to stop all your VM, unmount file sytem, then reduce the filesystem, then the LV. See for example :
http://www.hpuxtips.es/?q=node/194

As Udo said, you must have several GB free space in your volume group. Mine is for example :
Code:
--- Volume group ---
  VG Name               pve
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  7389
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               1,36 TB
  PE Size               4,00 MB
  Total PE              357182
  Alloc PE / Size       356416 / 1,36 TB
  Free  PE / Size       766 / 2,99 GB
  VG UUID               UcKh7L-rSyq-NYd5-Q12V-EP8I-7QbE-RD5z4M

Note the 'Free PE / Size 766 / 2,99 GB'

Alain
 
Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this

Hi,
on a standard-installation you have 4GB free space on the pve-vg for backup (snapshot).
Your trouble can have some possible causes:
1. your backup-volume is on the same vg (e.g. backup to the root-filesystem).
2. your snapshot are to big - or an second snapshot exist.
3. you use the full space of the vg for your filesystems (data, root, swap...)

Look with lvdisplay for snapshots.

Udo

Ok, this is it:

~# lvdisplay --- Logical volume ---
LV Name /dev/pve/data
VG Name pve
LV UUID YTr9Ga-89m0-EWQL-Qgcg-G9KV-sj8V-Dmwph8
LV Write Access read/write
LV Status available
# open 1
LV Size 1,80 TB
Current LE 471675
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
 
Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this

Ok, this is it:

~# lvdisplay --- Logical volume ---
LV Name /dev/pve/data
VG Name pve
LV UUID YTr9Ga-89m0-EWQL-Qgcg-G9KV-sj8V-Dmwph8
LV Write Access read/write
LV Status available
# open 1
LV Size 1,80 TB
Current LE 471675
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
Hi,
this show that you have an installation on top of lenny - it's ok, but you should know what you do (for pve-beginners is the standard-installation the better way). Like Alain wrote, you need free space in the VG - so you must shrink your pve/data, or extend your VG.
The normal free size is 4GB - if your VMs heavy used during backup you need perhaps more.

Udo
 
Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this

Ok, I am an beginner ;-)
This is a server which is installed with promox by OVH. So, I didn't installed the proxmox myself. I have 3 virtual servers (own installations) running on it, so: they must be alive..
(they can be offline for a a short time, but not too long).
I really don't know how I must fix this, as you said: you must know what to do ;-)
I hope you can help me ? Would be great !!!
 
Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this

Ok, I am an beginner ;-)
This is a server which is installed with promox by OVH. So, I didn't installed the proxmox myself...
Hi,
in this case you should ask OVH, why they don't leaf enough free space in the VG for backup - they should also have the knowledge to solve they mistake.

Udo
 
Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this

Meanwhile, you can do your backup by stopping your VM : vzdump --stop ....

Alain