332
edits
Changes
Jump to navigation
Jump to search
Line 31:
Line 31: + + + + + + +
no edit summary
The explanation why device file cannot be dumped and restored in a generic way is two fold. First of all, application can be dumped for live migration and on restore there can be no such device. But that's easy. Other than this, we don't know how all the devices work. App might have loaded some state into it, and in order to dump it properly we need to fetch that state. This is not something that can be done in a generic manner.
The explanation why device file cannot be dumped and restored in a generic way is two fold. First of all, application can be dumped for live migration and on restore there can be no such device. But that's easy. Other than this, we don't know how all the devices work. App might have loaded some state into it, and in order to dump it properly we need to fetch that state. This is not something that can be done in a generic manner.
=== Open files from unmounted filesystem ===
When a busy filesystem is "lazy" unmounted any references to it are cleaned up as soon as the filesystem is not busy anymore.
If a process has an open file from a lazy-umounted filesystem, CRIU just can't checkpoint/restore this process, unless the file is closed.
''See also: [[Dumping files]]''
=== Tasks with debugger attached ===
=== Tasks with debugger attached ===