[CRIU] procfs reports unexpected mnt_id and path for overlayfs files

[Saied Kazemi]

Andrew, thank you for reporting and providing an easy way to reproduce the
problem.

Miklos, thanks for the quick reply.  If you'd like to see the issue with
checkpointing and restoring Docker containers using OverlayFS, you can use
the docker binary here  https://github.com/SaiedKazemi/docker/releases.

--Saied




On Wed, Apr 15, 2015 at 8:07 AM, Miklos Szeredi <miklos at szeredi.hu> wrote:

> On Wed, Apr 15, 2015 at 10:50 AM, Andrew Vagin <avagin at odin.com> wrote:
> > Hello Miklos and Everyone else,
> >
> > We have a report that a container with overlayfs can't be checkpointed.
> >
> > To dump file descriptors we get information from /proc/pid/fd/ and
> /proc/pid/fdinfo.
> >
> > But in case of overlayfs we see unexpected values there.
> >
> > /proc/PID/fdinfo/FD contains mnt_id which isn't presented in
> /proc/pid/mountinfo.
> > /proc/PID/fd/FD does not contain an absolute path to the opened file.
> >
> > Can someone help to fix these issues?
>
> See this:
>
> https://lkml.org/lkml/2015/3/20/372
>
> Al didn't like that patch.  But it definitely will be fixed, one way
> or the other, in the near future.
>
> Thanks,
> Miklos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20150415/d885b79f/attachment-0001.html>