-
Notifications
You must be signed in to change notification settings - Fork 596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error (criu/files.c:1210): Unable to open fd=9 id=0x4d #1251
Comments
Please run it with |
[root@localhost criu]# ./criu-ns restore -j -D ./graph500-ckpt/ --tcp-establis |
The directory |
I have tried it , but nothing changed with the same error .. Can CRIU create the file if found missing or in bad mode? |
No, because it is not only about the existence of a file it should have the correct content or your restored process can fail in strange ways. Randomly creating files does not make sense. The CRIU checks exists to avoid undefined behavior. |
Restore error for lsm profile.... Is it necessary to check this? Or how to work around? thanks (14.067330) 47750: Opening 0x00fffface42000-0x00ffffad243000 0000000000000000 (81) vma |
@Qinghe12 That sounds like another problem. I am closing this. Please open a new ticket with exact information about the commands you are running. |
Restore failed issue
Can I know which file I need to restore normally migrating to another machine?
[localhost criu]# ./criu-ns restore -j -D ./graph500-ckpt/ --tcp-establish
['./criu-ns', 'restore', '-j', '-D', './graph500-ckpt/', '--tcp-established']
[ 1174.512830] new mount options do not match the existing superblock, will be ignored
45859: Error (criu/files.c:1210): Unable to open fd=9 id=0x4d
Error (criu/cr-restore.c:1479): 45859 killed by signal 9: Killed
Error (criu/cr-restore.c:1479): 45910 killed by signal 9: Killed
Error (criu/cr-restore.c:2397): Restoring FAILED.
The text was updated successfully, but these errors were encountered: