Mirror
/
mergerfs
mirror of https://github.com/trapexit/mergerfs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1362 Commits
48 Branches
99 Tags
46 MiB
 
 
 
 
Tree: 8c649d33ee
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '8c649d33ee'
${ noResults }
mergerfs/mkdocs/docs/config/flush-on-close.md

910 B
Raw Blame History

flush-on-close

By default, FUSE would issue a flush before the release of a file descriptor. This was considered a bit aggressive and a feature added to give the FUSE server the ability to choose when that happens.

  • flush-on-close=always
  • flush-on-close=never
  • flush-on-close=opened-for-write
  • Defaults to opened-for-write.

For now it defaults to opened-for-write which is less aggressive than the behavior before this feature was added. It should not be a problem because the flush is really only relevant when a file is written to. Given flush is irrelevant for many filesystems in the future a branch specific flag may be added so only files opened on a specific branch would be flushed on close.

References