[CRIU] Updating conf or changes in files generate "Error: Restoring failed"

[Pavel Emelyanov]

On 11/26/2014 10:45 AM, Roberto Del Aguila Rivera wrote:
> Thanks Pavel. The change in the file was made by hand and it was even an error. What we
> have clear now is that every file involved with Apache should not be changed to avoid this
> errors. The only question is, what happens if we continue using Apache from the first 
> restore and it's Apache who made the changes to the logs or to the confs? We haven't tried
> that but we are wondereing if it will happens the same error. 

In the reg-file.img file there are a set of paths to files
that are in use by processes. You can read this file with
the criu show -f reg-file.img command. The size field (if
present) denotes the size of the respective file at the time
of dump. If on restore the size will differ, criu will fail
to restore from such images.

Do you really need to change files by hands between dump
and restore? If this is a valid use-case we can teach criu
to bear with this.

> Thaks in advance.
> Roberto.
> 
> 
> 
> 2014-11-25 13:06 GMT-06:00 Pavel Emelyanov <xemul at parallels.com <mailto:xemul at parallels.com>>:
> 
>     On 11/25/2014 11:47 AM, Roberto Del Aguila Rivera wrote:
>     > Thanks a lot Pavel. (I don't know if it's ok to copy this large file here).
>     >
>     > ...
>     > (00.039488)   2001: Error (files-reg.c:820): File var/log/apache2/error.log has bad size 109 (expect 100)
>     > (00.039560) Error (cr-restore.c:1780): Restoring FAILED.
> 
>     OK, here it is. The file size has changed. We have this check to try
>     to make sure filesystem is in the same state as it used to be on dump,
>     so that applications can continue working.
> 
>     Can you describe what you're trying to do with apache, why has
>     the error.log's size has changed in such a strange way (plus
>     9 bytes)?
> 
>     Thanks,
>     Pavel
> 
>