mirrors/libfuse
0
0
Fork 0
mirror of https://github.com/libfuse/libfuse.git synced 2024-11-23 12:14:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

Document risks of auto_unmount (#763)

Browse Source
This commit is contained in:
Nikolaus Rath 2023-04-04 22:20:19 +01:00 committed by GitHub
parent 7be56c57f9
commit 4cf25c27f8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/mount.fuse3.8
View File

@ -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.