OpenVZ Forum: Support » Problem with vzdump and libattr.so.1.1.0

Home » General » Support » Problem with vzdump and libattr.so.1.1.0 (When running vzdump with --suspend, it semi-fails for some reason)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Problem with vzdump and libattr.so.1.1.0 [message #45531]

Wed, 14 March 2012 16:59

tjosten
Messages: 4
Registered: March 2012

Junior Member

Hi,

I discovered an inconvenience with vzdump-1.2.

When running

vzdump --suspend <CTID>

, it does not include the /lib/libattr.so.1.1.0 file to the tarball. This file does even not exist in the .tmp-directory created for the backup when running vzdump --suspend.

It says:

Quote:

Nov 16 12:17:33 INFO: File list transfer time: 0.000 seconds
Nov 16 12:17:33 INFO: Total bytes sent: 12730442
Nov 16 12:17:33 INFO: Total bytes received: 965523
Nov 16 12:17:33 INFO: sent 12730442 bytes received 965523 bytes 39187.31 bytes/sec
Nov 16 12:17:33 INFO: total size is 12584105731 speedup is 918.82
Nov 16 12:17:33 INFO: final sync finished (349 seconds)
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'
Nov 16 12:17:37 INFO: tar: ./lib/libattr.so.1.1.0: Warning: Cannot stat: No such file or directory
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)

(Please ignore the date, this is an older logfile but the output is still the same.)

In my original file system, libattr.so.1.1.0 is the target of the libattr.so.1 symlink which actually does exist in the .tmp directory (..but is linking to the file libattr.so.1.1.0 which does not exist as you just read.)

Finally, when running the backup without the suspend option, everything goes fine. I wonder if I am the only one with this problem as this is highly reproducible with every template I've tried (Debian, Ubuntu, Gentoo, Suse)

Any thoughts?

Best,
Timo

Report message to a moderator