Closed erulabs closed 2 years ago
Error in `criu': free(): invalid pointer: 0x00007f2dfd5c0bf0
this issue was fixed in 4d3ae51725552a38a2b5a9f0ba2c83e0d1fab89d
Cc: @Snorch
I'm diving into CRIU and would appreciate any hints, but Im wondering why this file in particular has to be "remapped", and what I can do to prevent that.
It means that one of processes has a file descriptor to this file, but this file was unlinked from a file system. You can use "lsof | grep '(deleted)'" to find such files. https://criu.org/How_hard_is_it_to_open_a_file
(00.300582) 1: mnt: Mounting fuse @/tmp/.criu.mntns.s8pOlp/12-0000000000/app/available_modules (0)
Is it a fuse mount? CRIU doesn't support fuse mounts. Why do we not return an error on dump?
Hrm, the filesystem is read-only, so that file certainly shouldn't have been deleted. It still exists on the host, at least. Will keep investigating, thanks!
A friendly reminder that this issue had no activity for 30 days.
Hello!
I'm having an issue restoring checkpoints that require ghost files on a read-only filesystem to be "remapped". A ghost file is created (from
restore.log
):And then fails when unlink fails:
I'm diving into CRIU and would appreciate any hints, but Im wondering why this file in particular has to be "remapped", and what I can do to prevent that. Is CRIU snapshotting a process which has a filehandle open to a read-only filesystem supported? I'm trying to understand what about this file causes criu to consider it a ghost file. Would love some help in understanding this behavior.
I believe the problem is that the "Ghost isnt found": https://github.com/checkpoint-restore/criu/blob/0509bc9f177bc38a574c274452dc106b95741ee9/criu/files-reg.c#L385-L393 for this particular file. I suspect this is my real issue?
I've tested this on CRIU v3.6, kernel 4.4 and 4.10, docker version 17.03.1-ce and 17.03.2-ce.
The error returned by Docker server:
The CRIU error:
The full restore.log
Any help is appreciated! Thanks!