vzdump keeps failing

  • Thread starter Thread starter jpcentanni
  • Start date Start date
J

jpcentanni

Guest
We are having problems with the backups on one of our proxmox servers. I've rebooted the proxmox server and it usually clears up for awhile, but then starts to happen again after about 3-4 weeks and then I have to reboot again. Here is the error:

2060: Jan 11 22:00:03 INFO: Starting Backup of VM 2060 (openvz)
2060: Jan 11 22:00:03 INFO: CTID 2060 exist mounted running
2060: Jan 11 22:00:03 INFO: status = CTID 2060 exist mounted running
2060: Jan 11 22:00:04 INFO: backup mode: snapshot
2060: Jan 11 22:00:04 INFO: ionice priority: 7
2060: Jan 11 22:00:04 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-ibd-vz-1-0')
2060: Jan 11 22:00:04 INFO: Insufficient free extents (1022) in volume group pve: 1024 required
2060: Jan 11 22:00:04 ERROR: Backup of VM 2060 failed - command 'lvcreate --size 4096M --snapshot --name vzsnap-ibd-vz-1-0 /dev/pve/data' failed with exit code 5


We have 19 containers running on this server and the back fails for all of them.

Any suggestions?
 
Do you have the standard 4GB of free space in VG?
# vgdisplay
should show a line like:
Free PE / Size 1022 / 3.99 GB
that is used by snapshot backup to create the temporary vzsnap lv. Seems you don't have enough space so the lvcreate --size 4096M above fails.
 
I did vgdisplay and it looks like its set to 4GB

VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 14338
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 407.87 GB
PE Size 4.00 MB
Total PE 104414
Alloc PE / Size 103392 / 403.88 GB
Free PE / Size 1022 / 3.99 GB
VG UUID 6rnjv4-pinw-5Ot1-GmcZ-ITo4-o72q-MT0ob4

Any other thoughts?
 
Mmmm I'm not a guru, but I see a strange thing, the Free size is 1022, while vzdump tries to allocate 1024.
First suggestion would be to set in /etc/vzdump.conf the value (or sligtly less):
size: 1022
(see 'man vzdump' for details) and then hope Tom notices this issues and is able to tell if vzdump default has changed, or why we both have 1022 free.
 
I'll give it a shot and see what happens.

I have my vzdump.conf file set to "size: 4096" just because I was getting full snapshots left and right so I figured (maybe mistakenly) that the higher the better.
 
Oh, I see... in fact, I was wrong, since 'Free PE size 1022' is NOT MB, but some other unit of measure, that totals of 3.99 GB, while you are requiring 4! (probably equal to 1024 of the other unit).
So NO bugs here (just to reassure Tom and Dietmar) :)
 
I don't mean to sound stupid, but which free space? Data? Root? Swap?