[CRIU] dedup and memory tracking

[J F]

>
> Provided you use the --track-mem and --prev-images options, the behavior is
> not expected to be like this. BTW, there was a bug on the 'Incremental
> dump'
> page -- the --track-mem option should be used always


Yes, I'm doing

sudo ./criu-main-branch/criu/crtools dump --tree $pid --tcp-established
--shell-
job --images-dir /mnt/mydata/$dumpdir --leave-running --track-mem

followed by 2nd dump:

sudo ./criu-main-branch/criu/crtools dump --tree $pid --tcp-established
--shell-
job --prev-images-dir /mnt/mydata/$prevdumpdir --images-dir
/mnt/mydata/$newdump
dir --leave-running --track-mem --auto-dedup

Do you have memory tracker compiled in the kenrel? The "criu check" option
> can check this, what does it tell?
>

/mnt/mydata/criu-main-branch/criu$ sudo ./crtools check
Looks good.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140611/f38ed13c/attachment.html>