<div dir="ltr"><div><div><div><div>Yes.<br></div>@Tycho: i have asked this question on the list:<br><br><br><i><span lang="en"><span>On what depends</span> <span>the size of a</span> <span>checkpoint</span> <span>of a container</span><span>?</span> <span>the</span> <span>size of data</span> <span>that are in</span> <span>the</span> <span>container ? <br></span></span><span lang="en"><span>if i increase the size of data in a container, the snapshot's size increase ?</span></span></i><br><br></div>and you have said:<br><br><i>The size of the RAM, lxc-checkpoint is a frontend for CRIU, and CRIU<br>dumps only memory state (well, and "ghost" file state). </i><br><br></div>i have asked this question because, when i increase the size of my program at runtime, then dumping process, the size of a snapshot is still the same for different sizes. <br><br></div>I have tested now. instead of lxc-attach, i have used ssh and the size of a snapshot changes increases :) <br><div><br><br><div>Bests. <br></div><div><span style="background:none repeat scroll 0% 0% yellow"></span>
<br><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-22 18:54 GMT+01:00 Tycho Andersen <span dir="ltr"><<a href="mailto:tycho.andersen@canonical.com" target="_blank">tycho.andersen@canonical.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Jan 22, 2015 at 05:49:50PM +0100, Thouraya TH wrote:<br>
> Yes, it is fine with *ssh* and without *lxc-attach* :)<br>
<br>
</span>Right, I guess this is the same problem as in the other thread (i.e.<br>
the dump fails because the attached process is in a different group)?<br>
<span class="HOEnZb"><font color="#888888"><br>
Tycho<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> Thanks a lot :)<br>
> Bests.<br>
><br>
> 2015-01-22 17:47 GMT+01:00 Pavel Emelyanov <<a href="mailto:xemul@parallels.com">xemul@parallels.com</a>>:<br>
><br>
> > On 01/22/2015 07:41 PM, Thouraya TH wrote:<br>
> > > *Dumping Process* with - s option:<br>
> > ><br>
> > > root@g-9:/home# lxc-checkpoint *-s *-D /home/ImGLXC1Worker -n worker<br>
> > > root@g-9:/home# lxc-ls -f<br>
> > > NAME STATE IPV4 IPV6 GROUPS AUTOSTART<br>
> > > -----------------------------------------------<br>
> > > worker *STOPPED* - - - NO<br>
> > ><br>
> > > *I have done this test:*<br>
> > > You have said: "/Check the file contents *after dump* but *before<br>
> > restore*. Does this file exists<br>
> > > at all? Does it contain proper data?/"<br>
> > ><br>
> > > 1) dumping Process with -s option<br>
> > > 2) root@g-9:/home/ImGLXC1Worker1# lxc-start -n worker<br>
> > > root@g-9:/home/ImGLXC1Worker1# lxc-ls -f<br>
> > > NAME STATE IPV4 IPV6 GROUPS AUTOSTART<br>
> > > -----------------------------------------------------<br>
> > > worker RUNNING 10.0.3.109 - - NO<br>
> > > worker1 STOPPED - - - NO<br>
> > > root@g-9:/home/ImGLXC1Worker1# ssh ubuntu@$(sudo lxc-info -n worker -H<br>
> > -i)<br>
> > > ..............<br>
> > > ubuntu@worker:/home$ vim results.txt<br>
> > ><br>
> > > *the file exists and contains the proper data.*<br>
> > ><br>
> > > 3) i stopped the container to test the restart:<br>
> > > root@g-9:/home/ImGLXC1Worker1# lxc-stop -n worker<br>
> > > root@g-9:/home/ImGLXC1Worker1# lxc-ls -f<br>
> > > NAME STATE IPV4 IPV6 GROUPS AUTOSTART<br>
> > > -----------------------------------------------<br>
> > > worker STOPPED - - - NO<br>
> > > worker1 STOPPED - - - NO<br>
> > > root@g-9:/home/ImGLXC1Worker1# *lxc-checkpoint -r* -D<br>
> > /home/ImGLXC1Worker1 -n worker<br>
> > > root@g-9:/home/ImGLXC1Worker1# ssh ubuntu@$(sudo lxc-info -n worker<br>
> > -H -i)<br>
> > > ^C<br>
> > > root@g-9:/home/ImGLXC1Worker1#<br>
> > > root@g-9:/home/ImGLXC1Worker1# lxc-ls -f<br>
> > ><br>
> > > ^CTraceback (most recent call last):<br>
> > > File "/usr/bin/lxc-ls", line 432, in <module><br>
> > > containers = get_containers(root=True)<br>
> > > File "/usr/bin/lxc-ls", line 261, in get_containers<br>
> > > if container.controllable:<br>
> > > KeyboardInterrupt<br>
> > ><br>
> > > *it's blocked!! *<br>
> ><br>
> > This should be forwarded to LXC guys.<br>
> ><br>
> > > *I proceeded as follows and the test process in the container restarts<br>
> > correctly:<br>
> > ><br>
> > > Restart* (after dumping process without starting and stopping the<br>
> > container)<br>
> > ><br>
> > > root@g-9:/home# lxc-checkpoint -r -D /home/ImGLXC1Worker -n worker<br>
> > > root@g-9:/home# lxc-ls -f<br>
> > > NAME STATE IPV4 IPV6 GROUPS AUTOSTART<br>
> > > -----------------------------------------------------<br>
> > > worker RUNNING 10.0.3.109 - - NO<br>
> > > worker1 STOPPED - - - NO<br>
> > > root@g-9:/home# ssh ubuntu@$(sudo lxc-info -n worker -H -i)<br>
> > > ..............<br>
> > > ubuntu@worker:/home$ vim results.txt<br>
> > ><br>
> > > i find the old and the new results in the file :)<br>
> ><br>
> > So everything is fine, isn't it?<br>
> ><br>
> > Thanks,<br>
> > Pavel<br>
> ><br>
> ><br>
<br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> CRIU mailing list<br>
> <a href="mailto:CRIU@openvz.org">CRIU@openvz.org</a><br>
> <a href="https://lists.openvz.org/mailman/listinfo/criu" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
<br>
</div></div></blockquote></div><br></div>