From 7abe98f1914213c60f90c3d52d49d43a0eb4225a Mon Sep 17 00:00:00 2001 From: Dietmar Maurer Date: Wed, 21 Mar 2012 06:42:37 +0100 Subject: [PATCH] vzdump: do not use tar flag --ignore-failed-read This flag is quite dangerous. For example when LVM snapshot runs full, we end up with an archive containing files with zero length (containig no data at all). --- PVE/VZDump/OpenVZ.pm | 2 +- debian/changelog.Debian | 6 ++++++ defines.mk | 2 +- 3 files changed, 8 insertions(+), 2 deletions(-) diff --git a/PVE/VZDump/OpenVZ.pm b/PVE/VZDump/OpenVZ.pm index fc12ccf38..a185f61b7 100644 --- a/PVE/VZDump/OpenVZ.pm +++ b/PVE/VZDump/OpenVZ.pm @@ -240,7 +240,7 @@ sub archive { my $srcdir = $self->{vmlist}->{$vmid}->{dir}; my $snapdir = $task->{snapdir}; - my $taropts = "--totals --sparse --numeric-owner --no-recursion --ignore-failed-read --one-file-system"; + my $taropts = "--totals --sparse --numeric-owner --no-recursion --one-file-system"; # note: --remove-files does not work because we do not # backup all files (filters). tar complains: diff --git a/debian/changelog.Debian b/debian/changelog.Debian index 223e66480..16150c2a7 100644 --- a/debian/changelog.Debian +++ b/debian/changelog.Debian @@ -1,3 +1,9 @@ +pve-manager (2.0-43) unstable; urgency=low + + * vzdump: do not use tar flag --ignore-failed-read + + -- Proxmox Support Team Wed, 21 Mar 2012 06:42:07 +0100 + pve-manager (2.0-42) unstable; urgency=low * use Digest::SHA instead of Digest::SHA1 diff --git a/defines.mk b/defines.mk index b6681d6be..fc57bdd02 100644 --- a/defines.mk +++ b/defines.mk @@ -2,7 +2,7 @@ RELEASE=2.0 VERSION=2.0 PACKAGE=pve-manager -PACKAGERELEASE=42 +PACKAGERELEASE=43 BINDIR=${DESTDIR}/usr/bin PERLLIBDIR=${DESTDIR}/usr/share/perl5