Proxmox/pve-manager
5
0
Fork 0
Code Pull Requests Releases Activity

vzdump: do not use tar flag --ignore-failed-read

Browse Source 
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).
This commit is contained in:
Dietmar Maurer 2012-03-21 06:42:37 +01:00
parent 3d6d8258bd
commit 7abe98f191
3 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
PVE/VZDump/OpenVZ.pm
View File

@ -240,7 +240,7 @@ sub archive {
my $srcdir = $self->{vmlist}->{$vmid}->{dir}; my $srcdir = $self->{vmlist}->{$vmid}->{dir};
my $snapdir = $task->{snapdir}; 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 # note: --remove-files does not work because we do not
# backup all files (filters). tar complains: # backup all files (filters). tar complains:

6
debian/changelog.Debian vendored
View File

@ -1,3 +1,9 @@
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 pve-manager (2.0-42) unstable; urgency=low
* use Digest::SHA instead of Digest::SHA1 * use Digest::SHA instead of Digest::SHA1

2
defines.mk
View File

@ -2,7 +2,7 @@ RELEASE=2.0
VERSION=2.0 VERSION=2.0
PACKAGE=pve-manager PACKAGE=pve-manager
PACKAGERELEASE=42 PACKAGERELEASE=43
BINDIR=${DESTDIR}/usr/bin BINDIR=${DESTDIR}/usr/bin
PERLLIBDIR=${DESTDIR}/usr/share/perl5 PERLLIBDIR=${DESTDIR}/usr/share/perl5