Article ID: 3031, created on Nov 2, 2007, last review on May 3, 2014

  • Applies to:
  • Virtuozzo containers for Linux

Symptoms

Trying to create backup of VE using 'vzbackup' utility I am getting messages like these:

2007-10-31T14:05:33-0400 vzbackup(30768): Error while example.net backup. Please  see /vz/backups/example.net/example.net.log for detailes.
2007-10-31T14:05:33-0400 vzbackup(30768): No VEs intended for backup found on example.net.
2007-10-31T14:05:33-0400 vzbackup(30768): Cleaning up...

Cause

Please have a look at 'vzbackup' log which is mentioned in output above - /vz/backups/example.net/example.net.log:

/usr/share/vzbackup-3.0.0-16.swsoft/vzbackup1: line 566: 30887 File size limit exceeded
tar cf "${OUTFILE}" ${TAR_OPT} ${TRACK_OPT} ${INCR_OPTIONS} ${DESC_OPTIONS} ${CONF_OPTIONS} ${QUOTA_OPTIONS} -C "$(dirname "${VE_PRIVATE}")" "$(basename "${VE_PRIVATE}")"
2007-10-31T13:57:36-0400 vzbackup1 (example.net:109): Tar error(153). Exiting...


It could happed when you are trying to backup VE whose size exceeds file size limit of underlying filesystem. E.g. file size limit for ext3 filesystem formatted with 1k block size is 16GB and 'tar' utility which is used to create backup of VE just can not create tarball if size of VE is more than 16GB.

Filesystem block size may be checked using this command on server:
tune2fs -l $BLOCK_DEVICE|grep "Block size"

where $BLOCK_DEVICE in the command above is the partition which is defined in BACKUP_DIR parameter in the file /etc/vzbackup.conf, it defines where Virtuozzo will put backups of VEs.

Resolution

The possible solutions to the problem with file size limit are:

- backup VE to another partition on the same hardware node with bigger block size or to another hardware node which has partition(s) formatted with bigger block size;
or
- reformat partition where Virtuozzo is going to store backups of VEs with bigger block size, e.g. 4k. It may be done using Linux system utility 'mke2fs' with '-b4096' parameter. Attention - all data on partition being formatted will be lost.

e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF