[PVE-User] WG: vzdump fails with ext code 141

[James Mills]

Hi Holger,

Yeah I've read the same post. Not so helpful. This has occurred twice in a
row for us now. I don't believe it's a gzip error though where the dusk is
becoming full, etc. I'll double check.

Still have no solution (yet)

cheers
James

Sent from my iPad

On 25/10/2011, at 22:54, Holger Ernst <he at ernstdatenmedien.de> wrote:

 Hi James,

i found such an issue in the forum:

http://forum.proxmox.com/threads/6874-vzdump-fails-failed-with-exit-code-141?highlight=vzdump+fails+with+ext+code+141

Not too helpfull, i know. It cured itself...

But as i understand the real error is gzip: stdout: Unknown error 512
Disk full? Network connection lost?

Regards, Holger

###########################################################
Hi All,

We have a problem with backups for one of our VMs
on a production cluster running ProxMox VE 1.8

Here is an excerpt of the logs:

107: Oct 22 00:52:11 INFO: Starting Backup of VM 107 (openvz)
107: Oct 22 00:52:11 INFO: CTID 107 exist mounted running
107: Oct 22 00:52:11 INFO: status = CTID 107 exist mounted running
107: Oct 22 00:52:11 INFO: backup mode: snapshot
107: Oct 22 00:52:11 INFO: ionice priority: 7
107: Oct 22 00:52:11 INFO: creating lvm snapshot of /dev/mapper/pve-data
('/dev/pve/vzsnap-vz1-0')
107: Oct 22 00:52:11 INFO: Logical volume "vzsnap-vz1-0" created
107: Oct 22 00:52:12 INFO: creating archive
'/mnt/pve/nfs_backup/vzdump-openvz-107-2011_10_22-00_52_11.tgz'
107: Oct 22 02:40:50 INFO: gzip: stdout: Unknown error 512
107: Oct 22 02:40:51 INFO: Logical volume "vzsnap-vz1-0" successfully
removed
107: Oct 22 02:40:52 ERROR: Backup of VM 107 failed - command '(cd
/mnt/vzsnap0/private/107;find . '(' -regex '^\.$' ')' -o '(' -type 's'
-prune ')' -o -print0|sed 's/\\/\\\\/g'|tar czpf - --totals --sparse
--numeric-owner --no-recursion --ignore-failed-read --one-file-system --null
-T -) >/mnt/pve/nfs_backup/vzdump-openvz-107-2011_10_22-00_52_11.dat' failed
with exit code 141

My research regarding this issue has lead
me to believe that it might be a bug with
the version of tar on the host system which
runs Debian 5.0.8 (lenny) (installed with the
ProxMox VE 1.8 ISO).

See: https://bugzilla.redhat.com/show_bug.cgi?id=487315

Basically I wants to know two things:

1) Has anyone encountered this problem before?
2) And if so, what was your solution?

I have been unable to find a later version of
tar available for Debian 5.0.8 (llenny) nor in
backports. I will keep looking for a solution myself
but it would be good to hear from others that use
ProxMox VE 1.8 in production.

kind regards,

James

-- 
  *James Mills
Systems Engineer* P:  07 3847 9292
E:  james.mills at overthewire.com.au
W: http://www.overthewire.com.au

_______________________________________________
pve-user mailing list
pve-user at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20111026/f4f65e71/attachment.htm>