D
Deleted member 1841
Guest
Hi,
I am experiencing an issue with vzdump-1.2. When creating a backup with
the backup returns the following errors:
Following scenario: After the 2nd sync, the files
do exist in the .tmp-directory created by rsync. As soon as the tar-command starts (sub archive in /usr/lib64/perl5/vendor_perl/5.12.4/PVE/VZDump/OpenVZ.pm) the symlinked file libattr.so.1.1.0 (which is missing referring to the error above) get's deleted. (I used "watch -n0 'ls -alh backup.tmp/lib/|grep attr" to discover this)
When not using --suspend but --stop (so no .tmp-dir with rsync gets created), everything works fine.
My /etc/vzdump.conf:
Any suggestions for this one?
I am experiencing an issue with vzdump-1.2. When creating a backup with
Code:
vzdump --suspend <CTID>
Code:
(...)
Nov 16 12:17:33 INFO: resume vm
Nov 16 12:17:33 INFO: Resuming...
Nov 16 12:17:33 INFO: vm is online again after 349 seconds
Nov 16 12:17:33 INFO: creating archive '/backup/vzdump-openvz-451-2011_11_16-11_30_04.tar'
[B]Nov 16 12:17:37 INFO: tar: ./lib/libattr.so.1.1.0: Warning: Cannot stat: No such file or directory
[/B]Nov 16 12:43:19 INFO: tar: /backup/vzdump-openvz-451-2011_11_16-11_30_04.tmp/lib: Cannot rmdir: Directory not empty
Nov 16 12:43:19 INFO: Total bytes written: 12858583040 (12GiB, 8.0MiB/s)
Nov 16 12:43:19 INFO: tar: Exiting with failure status due to previous errors
Nov 16 12:43:19 INFO: archive file size: 11.98GB
Nov 16 12:44:47 INFO: Finished Backup of VM 451 (01:14:43)
Following scenario: After the 2nd sync, the files
Code:
lrwxrwxrwx 1 root root 16 Feb 29 21:06 libattr.so.1 -> libattr.so.1.1.0
-rwxr-xr-x 1 root root 18K Feb 29 21:06 libattr.so.1.1.0
When not using --suspend but --stop (so no .tmp-dir with rsync gets created), everything works fine.
My /etc/vzdump.conf:
Code:
bwlimit: 0
size: 4096
Any suggestions for this one?