[CRIU] 355ae31 breaks p.haul
Pavel Emelyanov
xemul at parallels.com
Mon Sep 28 04:51:30 PDT 2015
On 09/28/2015 02:03 PM, Adrian Reber wrote:
> Commit 355ae31fa3f46e55b203eebb890c12ffbc3024e0 broke p.haul. If I
> revert it I can migrate processes again. With that commit included I see
> the following at the end of the dump:
>
> (00.015913) Dumping finished successfully
> (00.015926) Error (cr-service.c:91): Can't send response: Broken pipe
> (00.015928) Error (cr-service.c:486): Can't send response: Broken pipe
Wow. Thanks for the heads-up.
Andrey, would you take a look?
> p.haul continues to transfer the image but unpacking the image does not
> work:
>
> Waiting for images to unpack
> Exception in thread Thread-3:
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
> self.run()
> File "/share/p.haul/phaul/images.py", line 41, in run
> tf = tarfile.open(mode = "r|", fileobj = self.__sk.makefile())
> File "/usr/lib64/python2.7/tarfile.py", line 1690, in open
> **kwargs)
> File "/usr/lib64/python2.7/tarfile.py", line 1574, in __init__
> self.firstmember = self.next()
> File "/usr/lib64/python2.7/tarfile.py", line 2331, in next
> raise ReadError(str(e))
> ReadError: bad checksum
>
> Adrian
>
>
>
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu
>
More information about the CRIU
mailing list