<div dir="ltr"><div>unrecognized option `--enable-fs'<br><br></div>I'm using version 1.5.2<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 3, 2015 at 3:59 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"><div class="HOEnZb"><div class="h5">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>
</div></div>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>
<span class="HOEnZb"><font color="#888888"><br>
-- Pavel<br>
<br>
</font></span></blockquote></div><br></div>