Changes

Jump to: navigation, search

AutoFS

399 bytes added, 13:22, 30 June 2016
Limitations
CRIU supports both direct (offset) and indirect AutoFS mount points migration.
However, there is a limitation But CRIU reconstructs AutoFS mount point on restore with different device ID and root inode number.This leads to some limitations in migrating of systemd services using AutoFSAutofs.
The root of the limitation these limitations is that systemd saves AutoFS master (process, serving AutoFS requests from kernel side) can save AutoFS mount point device ID (and root inode number) in its internals and compares then compare saved value (s) with current one received ones on each AutoFS-related kernel request from kernel side, and if they . If these values do not match, it ignores can ignore the request.In user world it means that any access to such an AutoFS mount point will stuck.
CRIU reconstructs AutoFS mount point on restore with different device ID, thus systemd doesn't recognize it anymore.Known Autofs masters:
In user world it means that any access to # <code>systemd</code>: AutoFS-based services ::Systemd saves AutoFS mount point served by systemd will stuckdevice ID in its internals. ::Restart of the service solves this issue. # <code>automount</code>: Direct (offset) mounts  ::Automount saves AutoFS mount point device ID and root inode number for direct (offset) monuts in its internals.::Killing automount with SIGKILL and restarting it solves this issue.
== Tricks ==
36
edits

Navigation menu