Article ID: 124419, created on Feb 7, 2015, last review on Apr 7, 2015

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux 4.7

Symptoms

It is impossible to suspend (migrate, convert in online mode) a container which has tarversion older than 1.23 installed if it is running on a node with the kernel 2.6.32-042stab102.9.

~# vzctl suspend 101
Setting up checkpoint...
        suspend...
        dump...
Can not dump the Container: Invalid argument
Error: tar exited with 64
Failed to checkpoint the Container

Cause

The kernel 2.6.32-042stab102.9 uses a feature of a new tar (version 1.23 and newer) which is not supported by older tar versions.

For CentOS 4 Issue has been recognized as a product bug with internal ID #PSBM-32452. For CentOS 5 Issue has been recognized as a product bug with internal ID #PSBM-31038.

Resolution

For CentOS 4: The issue has not been fixed yet, as the tar exit code is not 64 but 2.

For CentOS 5: Issue is permanently fixed in a kernel 2.6.32-042stab103.6. Update kernel and reboot the node in order to address the issue.

If hardware node reboot is not an option at this moment you may resort to one of the following workarounds:

  1. Update tar inside of container to a version 1.23 or newer. (NB: tar 1.24 is broken, it cannot restore device files)
  2. Migrate/convert the container in offline mode.
  3. Prior to migration/conversion check all mounts using a tmpfs FS type. Unmount all nested mounts for tmpfs mount points, e.g. /dev/pts is considered as a nested mount for /dev.

Search Words

cannot dump

converting to ploop fails

Can not dump the Container: Invalid argument Error: tar exited with 64

tar exit code 64

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF