rt/mergerfs
1
0
Fork 0
mirror of https://github.com/trapexit/mergerfs.git synced 2026-10-26 19:01:56 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updates to docs, add nonraid, more intro to fs details (#1512)
Some checks are pending
CodeQL / Analyze (push) Waiting to run
Details
mkdocs / deploy (push) Waiting to run
Details

Browse source
This commit is contained in:
trapexit 2025-08-21 16:09:04 -04:00 • committed by GitHub
parent dd1bea52cd
commit 2101ef5bcc
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
8 changed files with 406 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

9
mkdocs/docs/faq/usage_and_functionality.md
View file

@ -1,5 +1,14 @@
# Usage and Functionality
## What happens when file paths overlap?
It depends on the situation and the configuration of mergerfs. The
user chooses the algorithm (policy) on how to behave when a particular
filesystem function is requested. Which file to select or act on.
See how [policies](../config/functions_categories_policies.md) work.
## Can mergerfs be used with filesystems which already have data?
Yes. mergerfs is really just a proxy and does **NOT** interfere with