diff options
author | Nikolaus Rath <Nikolaus@rath.org> | 2023-04-04 22:20:19 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-04-04 22:20:19 +0100 |
commit | 4cf25c27f89754e0e0310cb430dee0ddd9493c70 (patch) | |
tree | 29fb8d7e44779a03a183723ea37e3265adf8fcb6 | |
parent | 7be56c57f93e3436b1fbd9ecc320de5c03a3e4b8 (diff) | |
download | fuse-4cf25c27f89754e0e0310cb430dee0ddd9493c70.tar.gz |
Document risks of auto_unmount (#763)
-rw-r--r-- | doc/mount.fuse3.8 | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/mount.fuse3.8 b/doc/mount.fuse3.8 index 0cb0b5c..230c6af 100644 --- a/doc/mount.fuse3.8 +++ b/doc/mount.fuse3.8 @@ -146,6 +146,21 @@ responsible for releasing the mountpoint, which means that the mountpoint becomes inaccessible if the filesystem terminates without first unmounting. +This option is dangerous and should only be used after careful consideration of the +risks. + +Automatically unmounting the filesystem means that if the filesystem crashes the +mountpoint may suddenly appear empty, which may have unintended consequences. For example, +a running backup and mirroring program may conclude that all the data in the filesystem +has been deleted and proceed to propagate this deletion to the backup / remote system. If +the mountpoint instead becomes inaccessible (the default), most programs will behave +correctly (report an error). + +This feature may also accidentally unmount the wrong filesystem due to race +conditions. For example, if another filesystem was mounted underneath the same mountpoint, +or if a new filesystem is mounted after the FUSE process has crashed, it may accidentally +get unmounted. + At the moment, this option implies that the filesystem will also be mounted with \fBnodev\fP and \fBnosuid\fP (even when mounted by root). This restriction may be lifted in the future. |