[CRIU] dumping LXC 1.0 container failed - unable to open irmap-cache: No such file or directory

David Shwatrz dshwatrz at gmail.com
Wed Mar 5 05:54:33 PST 2014


Christopher,
Yes, you are absolutely right. In tests which I had done with a simple
process (not  in a containers environment), everything with c/r worked
fine, but this same message still appeared.

>Error (mount.c:430): Mount 327 (master_id: 2 shared_id: 0) has >unreachable sharing

Any ideas how can we tell to which mount/mount point is this message related ?

Regards.
DavidS



On Wed, Mar 5, 2014 at 2:55 PM, Christopher Covington
<cov at codeaurora.org> wrote:
> On 03/05/2014 05:32 AM, David Shwatrz wrote:
>> Hello,
>> I am trying to checkpoint an LXC 1.0 container and it fails.
>> I am trying it with crtools 1.2.
>>
>> The command I use is:
>> criu dump -t 4983 -v4 -D images --shell-job --ext-unix-sk -o dump.log
>> --tcp-established --file-locks
>> and the log file shows this as a first error:
>> unable to open irmap-cache: No such file or directory
>> the full log fine is in:
>> http://pastebin.com/e3MKxmBg
>
> The irmap stuff is spurious. This looks like your real error:
>
> Error (mount.c:430): Mount 327 (master_id: 2 shared_id: 0) has unreachable sharing
>
> Regards,
> Christopher
>
> --
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> hosted by the Linux Foundation.


More information about the CRIU mailing list