<div dir="ltr"><div>Can CRIU be used to checkpoint/restore a single process and not a process tree? I keep hitting this error message:<br></div><div><br></div><div><p style="margin:0px;font-family:Menlo"> <span style="color:rgb(206,121,36)">if</span> (item->sid == <span style="color:rgb(195,55,32)">0</span>) {</p>
<p style="margin:0px;font-family:Menlo;color:rgb(195,55,32)"><span style="color:rgb(0,0,0)"> pr_err(</span>"A session leader of <span style="color:rgb(213,59,211)">%d</span>(<span style="color:rgb(213,59,211)">%d</span>) is outside of its pid namespace<span style="color:rgb(213,59,211)">\n</span>"<span style="color:rgb(0,0,0)">,</span></p>
<p style="margin:0px;font-family:Menlo"> item->pid.real, item->pid.virt);</p>
<p style="margin:0px;font-family:Menlo"> <span style="color:rgb(206,121,36)">goto</span> err_cure;</p>
<p style="margin:0px;font-family:Menlo"> }</p><p style="margin:0px;font-family:Menlo"><br></p></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 4, 2015 at 2:18 AM, Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 06/03/2015 09:15 PM, CRIU criu wrote:<br>
> unrecognized option `--enable-fs'<br>
><br>
> I'm using version 1.5.2<br>
<br>
</span>Yes, the option appeared in 1.6, please, upgrade.<br>
<div class="HOEnZb"><div class="h5"><br>
> On Wed, Jun 3, 2015 at 3:59 AM, Pavel Emelyanov <<a href="mailto:xemul@parallels.com">xemul@parallels.com</a> <mailto:<a href="mailto:xemul@parallels.com">xemul@parallels.com</a>>> wrote:<br>
><br>
> On 06/03/2015 12:31 AM, CRIU criu wrote:<br>
> > Hello,<br>
> ><br>
> > I'm porting CRIU on Android.<br>
> ><br>
> > When I run CRIU, it fails with the following<br>
> > Error (mount.c:601): FS mnt ./cache dev 0x1f00002 root / unsupported id 28<br>
> ><br>
> ><br>
> > This is what I found in dump.log<br>
> ><br>
> > (00.096659) type ext4 source /dev/block/mtdblock0 mnt_id 0x26 s_dev 0x1f00000 / @ ./system flags 0x200001 options data=ordered<br>
> > (00.096844) type ext4 source /dev/block/mtdblock1 mnt_id 0x27 s_dev 0x1f00001 / @ ./data flags 0x406 options data=ordered<br>
> > (00.097010) type ext4 source /dev/block/mtdblock2 mnt_id 0x28 s_dev 0x1f00002 / @ ./cache flags 0x406 options data=ordered<br>
> ><br>
> > As seen, all (mtdblock*) is ext4 based, but CRIU complains about "cache" partition. Any clue as to why this is the case?<br>
> > I don't see ext4 in "static struct fstype fstypes[]"<br>
><br>
> Yes, because when restoring this mountpoint we will have incomplete info for<br>
> which device to use. When restoring on the same box, we should take the one<br>
> we saw on dump, but in case of live migration situation is unclear.<br>
><br>
> Can you try to use the "--enable-fs ext4" option and see whether it works<br>
> for you?<br>
><br>
> -- Pavel<br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>