github/mergerfs
4
0
Fork 0
mirror of https://github.com/trapexit/mergerfs.git synced 2026-10-21 05:01:34 +00:00
Code Issues Releases Wiki Activity

Add more details to project comparisons

Browse Source
This commit is contained in:
Antonio SJ Musumeci
2026-04-04 02:17:06 -05:00
committed by trapexit
parent f2c8e5d9eb
commit 3b10406f95
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mkdocs/docs/project_comparisons.md
+10 -4
View File
@@ -556,18 +556,24 @@ something like mergerfs is unable to be used.
policyfs is a Linux FUSE storage daemon that unifies multiple storage policyfs is a Linux FUSE storage daemon that unifies multiple storage
paths under a single mountpoint, similarly to mergerfs. Its paths under a single mountpoint, similarly to mergerfs. Its
distinguishing features are explicit path-pattern-based routing rules distinguishing features are explicit path-pattern-based routing rules
for reads and writes, and an optional SQLite metadata index that can for placement, and an optional SQLite metadata index that can serve
serve `readdir` and `getattr` operations without spinning up HDDs. `readdir` and `getattr` operations without spinning up HDDs.
Compared with mergerfs, policyfs emphasizes explicit path-based routing Compared with mergerfs, policyfs emphasizes explicit path-based routing
and optional metadata indexing, while mergerfs emphasizes a broad, and optional metadata indexing, while mergerfs emphasizes a broad,
policy-driven pooling model with longer operational history and wider policy-driven pooling model with longer operational history and wider
adoption. adoption. It doesn't try limiting spinup as doing so fundimentally is
in [conflict with other features.](faq/limit_drive_spinup.md)
Due to the nature of PolicyFS it can not really be used while changing
files out-of-band and with the delayed writeback of metadata and
unlinking there is a greater risk of inconsistancy in error
conditions.
* **Better than mergerfs for:** explicit path-based routing and optional * **Better than mergerfs for:** explicit path-based routing and optional
metadata indexing to reduce HDD spin-ups. metadata indexing to reduce HDD spin-ups.
* **Worse than mergerfs for:** users prioritizing project maturity, * **Worse than mergerfs for:** users prioritizing project maturity,
adoption, and long-established operational behavior. adoption, performance, and long-established operational behavior.
## Greyhole ## Greyhole