Bringing up FUSE mounts C/R support
summary
Adds checkpoint/restore for FUSE by building a proof‑of‑concept that spawns a fake FUSE daemon, performs the mount, stores the resulting device FD in fdstore, and later injects that FD into the restored real daemon — this demo works for simple FUSE filesystems. Uses spfs proxy (for NFS-like cases) and extracts per‑file node ID via file handle to preserve inode identity. Covers overlayfs kernel callback patches, mmap behavior (no early page faults), and outstanding problems: networked daemons, version compatibility and predump/stat caching.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:21Examples
- 2:38OverlayFS
- 12:58Demon Replacement
- 14:41Opening files
- 15:28Special structures
- 16:10FUSE node ID
- 18:45File mappings
- 20:55Dump
- 23:46Status
- 26:41Questions
related talks
24mFuse mounts recovery and Checkpoint/Restore
26mImprove FUSE Filesystem Performance and Reliability
19mExtension Framework for File Systems in User space
29mFilesystem mounts in user namespaces
16mA re-introduction to s3fs
19mFiles on Unmounted Mounts
17mCoFS: A Filesystem for Fast Container Startup
21mTowards High-availability for Virtio-fs