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

Misc docs updates (#1549)

Browse source
This commit is contained in:
trapexit 2025-10-24 20:47:33 -05:00 • committed by GitHub
parent 727c522fb8
commit 3bee0f0b57
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 30 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

11
mkdocs/docs/extended_usage_patterns.md
View file

@ -68,6 +68,11 @@ passthrough IO or other features.
### time based expiring
**NOTE:** this script is an **example**, not particularly efficient, and
really not intended for production deployments. Until such time that
mergerfs provides tooling for this usecase consider using
[mergerfs-cache-mover](https://github.com/monstermuffin/mergerfs-cache-mover).
Move files from cache filesystem to base pool which have an access
time older than the supplied number of days. Replace `-atime` with
`-amin` in the script if you want minutes rather than days.
@ -99,6 +104,12 @@ respectively.
### percentage full expiring
**NOTE:** this script is an **example**, not particularly efficient, and
really not intended for production deployments. Until such time that
mergerfs provides tooling for this usecase consider using
[mergerfs-cache-mover](https://github.com/monstermuffin/mergerfs-cache-mover).
While the cache filesystem's percentage full is above the provided
value move the oldest file from the cache filesystem to the base pool.

26
mkdocs/docs/known_issues_bugs.md
View file

@ -23,13 +23,18 @@
#### Supplemental group caching
Due to the overhead of
[getgroups/setgroups](http://linux.die.net/man/2/setgroups) mergerfs
utilizes a cache. As necessary the supplemental group information will
be queried and cached. That cached list of groups will be used to set
the supplement groups as necessary. Due to the high cost of querying
the group list the default expiry for said data is 1 hour and after 12
hours of no usage will be removed from the cache all together.
Due to the high cost of querying supplemental groups it is necessary
for mergerfs to cache the list. As a result if supplemental groups are
changed while mergerfs is running the cache may become stale. This
generally isn't a problem as these groups tend not to be changed
often. However, the cache has a default expiry of 1 hour and after 12
hours of no usage the cache entry will be removed altogether.
See [gidcache.expire-timeout and
gid-cache.remove-timeout](config/options.md) and the [runtime
interface](runtime_interface.md#commands) for forcing expiry and clearing of
the cache.
#### Host vs Container identity
@ -128,6 +133,13 @@ more compatible but could also be more performant in certain
situations.
### rsync
This isn't specific to mergerfs but when using `--sparse, -S` option
with rsync the block size used to read and write data changes from
256KiB to 1KiB. This significantly impacts performance.
### backup software
Some software, like borgbackup and others, leverage inodes as one of a