Fuse mounts recovery and Checkpoint/Restore
summary
Proposes adding a FUSE API to enable mount healing and CRIU-based checkpoint/restore by cleaning kernel-side FUSE state, dropping pending requests, and reinitializing connections while keeping mounts in place. Introduces connection generation to mark and invalidate stale iodes so lookups force a fresh lookup before open, and describes a tool to reuse file descriptor or reinit the connection. Identifies bind-mount corner cases (mountroute stale), libfuse iode mismatches that crash new daemons, and alternatives: persist FUSE state, NFSv4-style state recovery, or BPF tracking.
AI-written summary · about
chapters (8)
- 0:00Introduction to FUSE recovery
- 2:55FUSE demon crash problem
- 7:11Dentry revalidation mechanism
- 10:28Bind mount recovery issue
- 12:37Current limitations and next steps
- 13:43Community feedback and alternatives
- 18:41CFS and BPF perspectives
- 22:36Conclusion and future work
related talks
32mBringing up FUSE mounts C/R support
26mImprove FUSE Filesystem Performance and Reliability
21mTowards High-availability for Virtio-fs
19mExtension Framework for File Systems in User space
16meBPF-based FUSE
19mFiles on Unmounted Mounts
29mFilesystem mounts in user namespaces
16mA re-introduction to s3fs