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

@@ -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:

debian/changelog.Debian

+pve-manager (2.0-43) unstable; urgency=low
+
+  * vzdump: do not use tar flag --ignore-failed-read
+
+ -- Proxmox Support Team <support@proxmox.com>  Wed, 21 Mar 2012 06:42:07 +0100
+
 pve-manager (2.0-42) unstable; urgency=low
 
   * use Digest::SHA instead of Digest::SHA1

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