OpenVZ Forum


Home » General » Support » Undump error when restoring a container on shared storage
Undump error when restoring a container on shared storage [message #52392] Sun, 24 April 2016 21:52 Go to next message
MadMass is currently offline  MadMass
Messages: 2
Registered: April 2016
Location: France
Junior Member
From: *76.139.88.rev.sfr.net
Hi all,

I try to perform a checkpoint save/reload on a HN, with private data stored on a NFS share, thus i can't use ploop.
I can dump the CT without any problem, but when I try to restore it i have the following error :
root@serveur-2:/home/admin# vzctl restore 101 --undump --dumpfile ct_101
Restoring container ...
Container is mounted
        undump...
Adding IP address(es): xx.xx.xx.xx
Setting CPU units: 1000
Setting CPUs: 1
Restore error, undump failed: Not a directory
Error: can't open file /lib/x86_64-linux-gnu/libuuid.so.1.3.0
Error: do_rst_vma: rst_file: 7920264
Error: do_rst_mm: failed to restore vma 0x7fb081aac000-0x7fb081ab0000: -20
Error: do_rst_mm 8156528
Error: rst_mm: -20
Container restore failed
Container is unmounted

I tried with a debian-8 template and an ubuntu-15 template, without any difference. I've found another topic with a similar issue, but i haven't found any solution yet :
https://forum.openvz.org/index.php?t=msg&th=9653&S=a 4e20082ba8659075ffd49e564dec085

My OpenVZ kernel is : 2.6.32-openvz-042stab113.21-amd64

Anyone can't help be to resolve this problem ? Thanks for your help.
Re: Undump error when restoring a container on shared storage [message #52394 is a reply to message #52392] Tue, 26 April 2016 08:48 Go to previous message
MadMass is currently offline  MadMass
Messages: 2
Registered: April 2016
Location: France
Junior Member
From: *76.139.88.rev.sfr.net
I did some tests and i found that using NFS v3, it works fine. Thus it's related to NFSv4. I know that there were substantial modifications between the two versions, what could cause this kind of issue ?
Previous Topic: Container Ram size
Next Topic: Ploop error (ploop.c:1381)
Goto Forum:
  


Current Time: Mon Jul 22 22:25:37 GMT 2019