mirror of
https://github.com/trapexit/mergerfs.git
synced 2026-11-21 15:36:31 -05:00
Misc documentation updates (#1605)
Some checks failed
mkdocs / deploy (push) Has been cancelled
Some checks failed
mkdocs / deploy (push) Has been cancelled
This commit is contained in:
parent
0caae4fbf0
commit
965e26989c
6 changed files with 100 additions and 61 deletions
|
|
@ -31,7 +31,7 @@ level API.
|
||||||
Windows, while used for NAS systems more often than MacOS, is still
|
Windows, while used for NAS systems more often than MacOS, is still
|
||||||
relatively uncommon when compared to Linux. [Drive
|
relatively uncommon when compared to Linux. [Drive
|
||||||
Pool](../project_comparisons.md#stablebits-drivepool) is a good
|
Pool](../project_comparisons.md#stablebits-drivepool) is a good
|
||||||
alternative.
|
alternative. It may also be possible to use mergerfs with WSL.
|
||||||
|
|
||||||
|
|
||||||
## What filesystems can be used as branches?
|
## What filesystems can be used as branches?
|
||||||
|
|
@ -39,10 +39,11 @@ alternative.
|
||||||
ext4, btrfs, xfs, f2fs, zfs, nfs, etc.
|
ext4, btrfs, xfs, f2fs, zfs, nfs, etc.
|
||||||
|
|
||||||
Most any filesystem should work but there could be issues with
|
Most any filesystem should work but there could be issues with
|
||||||
non-POSIX compliant filesystems such as vfat, ntfs, cifs, exfat,
|
non-POSIX compliant filesystems such as nfs (w/ root squashing), vfat,
|
||||||
etc. When directories need to be created or files moved by mergerfs if
|
ntfs, cifs, exfat, etc. When directories need to be created or files
|
||||||
the filesystem returns errors due to not supporting certain POSIX
|
moved by mergerfs if the filesystem returns errors due to not
|
||||||
filesystem features it could result in the core functions failing.
|
supporting certain POSIX filesystem features it could result in the
|
||||||
|
core functions failing.
|
||||||
|
|
||||||
Since mergerfs is not generally used with non-POSIX filesystems this
|
Since mergerfs is not generally used with non-POSIX filesystems this
|
||||||
has not been a problem for users and there are some checks for known
|
has not been a problem for users and there are some checks for known
|
||||||
|
|
@ -51,6 +52,13 @@ filesystem results in issues please [file a
|
||||||
ticket](https://github.com/trapexit/mergerfs/issues) with the details.
|
ticket](https://github.com/trapexit/mergerfs/issues) with the details.
|
||||||
|
|
||||||
|
|
||||||
|
## What types of storage devices does mergerfs work with?
|
||||||
|
|
||||||
|
Since mergerfs works at the filesystem level rather than device level
|
||||||
|
there is no compatibility concerns based on the physical storage
|
||||||
|
devices involved.
|
||||||
|
|
||||||
|
|
||||||
## Can I use mergerfs without SnapRAID? SnapRAID without mergerfs?
|
## Can I use mergerfs without SnapRAID? SnapRAID without mergerfs?
|
||||||
|
|
||||||
[https://www.snapraid.it](https://www.snapraid.it)
|
[https://www.snapraid.it](https://www.snapraid.it)
|
||||||
|
|
@ -85,7 +93,7 @@ pool.
|
||||||
## Can mergerfs run via Docker, Podman, Kubernetes, etc.
|
## Can mergerfs run via Docker, Podman, Kubernetes, etc.
|
||||||
|
|
||||||
Yes. [See installation
|
Yes. [See installation
|
||||||
page.](../setup/installation.md##podman-docker-oci-containers)
|
page.](../setup/installation.md#podman-docker-oci-containers)
|
||||||
|
|
||||||
|
|
||||||
## How does mergerfs interact with user namespaces?
|
## How does mergerfs interact with user namespaces?
|
||||||
|
|
|
||||||
|
|
@ -68,6 +68,11 @@ underlying data. For more details as to why that is see the docs on
|
||||||
[inodecalc](../config/inodecalc.md).
|
[inodecalc](../config/inodecalc.md).
|
||||||
|
|
||||||
|
|
||||||
|
## Are there any size limitations to files, directories, etc.?
|
||||||
|
|
||||||
|
Whatever the limits are of the underlying filesystems.
|
||||||
|
|
||||||
|
|
||||||
## Do reflink, FICLONE, or FICLONERANGE work?
|
## Do reflink, FICLONE, or FICLONERANGE work?
|
||||||
|
|
||||||
Unfortunately not. FUSE, the technology mergerfs is based on, does not
|
Unfortunately not. FUSE, the technology mergerfs is based on, does not
|
||||||
|
|
|
||||||
|
|
@ -2,40 +2,43 @@
|
||||||
|
|
||||||
**mergerfs** is a [union
|
**mergerfs** is a [union
|
||||||
filesystem](https://en.wikipedia.org/wiki/Union_mount) that makes
|
filesystem](https://en.wikipedia.org/wiki/Union_mount) that makes
|
||||||
multiple storage devices or filesystems appear as a single unified
|
multiple filesystems and/or directories appear as a single unified
|
||||||
directory. Built on [FUSE (Filesystem in
|
directory. mergerfs is designed to simplify how you manage files
|
||||||
Userspace)](https://en.wikipedia.org/wiki/Filesystem_in_Userspace), it
|
across multiple independent filesystems without the complexity,
|
||||||
is designed to simplify how you manage files across several
|
fragility, or cost of RAID or similar storage aggregation
|
||||||
independent filesystems without the complexity, fragility, or cost of
|
technologies.
|
||||||
RAID or similar storage aggregation technologies.
|
|
||||||
|
|
||||||
Think of mergerfs as a smart pooling layer: you can combine any number
|
mergerfs as a smart pooling layer allows you to combine any number of
|
||||||
of [existing
|
[existing
|
||||||
filesystems](faq/usage_and_functionality.md#can-mergerfs-be-used-with-filesystems-which-already-have-data)
|
filesystems](faq/usage_and_functionality.md#can-mergerfs-be-used-with-filesystems-which-already-have-data);
|
||||||
— whether they are on hard drives, SSDs, network shares, or other
|
whether they are on hard drives, SSDs, network shares, or other
|
||||||
mounted storage — into what looks like one large filesystem, while
|
mounted storage; into what looks like one large filesystem, while
|
||||||
still maintaining direct access to each individual filesystem. Unlike
|
still maintaining direct access to each individual filesystem. Unlike
|
||||||
RAID, there's no rebuild process if a device fails. You only lose the
|
RAID, there's no rebuild process if a device fails. You only lose
|
||||||
files that were on that specific filesystem. You can also add or
|
those files that were on that specific filesystem. You can also add or
|
||||||
remove filesystems at any time without restructuring your entire pool.
|
remove filesystems at any time without restructuring the pool.
|
||||||
|
|
||||||
mergerfs excels at cost-effective storage expansion, making it ideal
|
mergerfs excels at cost-effective storage expansion, making it ideal
|
||||||
for media libraries, backups, archival data, and other write-sometimes,
|
for media libraries, backups, archival data, and other write-sometimes,
|
||||||
read-often workloads where you need lots of space but don't want
|
read-often workloads where you need lots of space but don't want
|
||||||
the overhead of traditional storage technologies.
|
the overhead of traditional storage aggregation technologies.
|
||||||
|
|
||||||
**Key advantages:**
|
**Key advantages:**
|
||||||
|
|
||||||
* Mix and match filesystems of any size, type, or underlying device
|
* Mix and match filesystems of any size,
|
||||||
|
[type](faq/compatibility_and_integration.md#what-filesystems-can-be-used-as-branches),
|
||||||
|
or [underlying
|
||||||
|
device](faq/compatibility_and_integration.md#what-types-of-storage-devices-does-mergerfs-work-with)
|
||||||
* No parity calculations or rebuild times
|
* No parity calculations or rebuild times
|
||||||
|
* Does not require hard drives to be spinning if not in use
|
||||||
* Add or remove filesystems on the fly
|
* Add or remove filesystems on the fly
|
||||||
* Direct access to files on individual filesystems when needed
|
* [Direct access to files](faq/usage_and_functionality.md#can-filesystems-still-be-used-directly-outside-of-mergerfs-while-pooled) on individual filesystems when needed
|
||||||
* Flexible policies for controlling where new files are created
|
* Flexible [policies](config/functions_categories_policies.md) for controlling where new files are created
|
||||||
|
|
||||||
For users seeking alternatives to mhddfs, unionfs, aufs, or DrivePool,
|
For users seeking alternatives to mhddfs, unionfs, aufs, or DrivePool,
|
||||||
mergerfs offers a mature, actively maintained solution with extensive
|
mergerfs offers a mature, actively maintained solution with extensive
|
||||||
configuration options and documentation. See the [project comparisons
|
configuration options and documentation. See the [project comparisons
|
||||||
for more comparisons.](project_comparisons.md)
|
for more details.](project_comparisons.md)
|
||||||
|
|
||||||
|
|
||||||
## Features
|
## Features
|
||||||
|
|
@ -71,13 +74,14 @@ for more comparisons.](project_comparisons.md)
|
||||||
* File whiteout
|
* File whiteout
|
||||||
* Splitting of files across branches
|
* Splitting of files across branches
|
||||||
* Active rebalancing of content
|
* Active rebalancing of content
|
||||||
|
* [Actively attempt to keep hard drives spun down](faq/limit_drive_spinup.md)
|
||||||
|
|
||||||
|
|
||||||
## How it works
|
## How it works
|
||||||
|
|
||||||
mergerfs logically merges multiple filesystem paths together. Not
|
mergerfs logically merges multiple filesystem paths together. Not
|
||||||
block devices, not filesystem mounts, just paths. It acts as a proxy
|
block devices, not filesystem mounts, just paths. It acts as a proxy
|
||||||
to the underlying filesystem paths. Combining the behaviors of some
|
to the underlying filesystem. Combining the behaviors of some
|
||||||
functions and being a selector for others.
|
functions and being a selector for others.
|
||||||
|
|
||||||
When the contents of a directory are requested mergerfs combines the
|
When the contents of a directory are requested mergerfs combines the
|
||||||
|
|
@ -138,3 +142,6 @@ Head to the [quick start guide](quickstart.md).
|
||||||
* The search feature of MkDocs is not great. Searching for "literal
|
* The search feature of MkDocs is not great. Searching for "literal
|
||||||
strings" will generally not work. Alernative solutions are being
|
strings" will generally not work. Alernative solutions are being
|
||||||
investigated.
|
investigated.
|
||||||
|
* While not intended for end users nor completely accurate some might
|
||||||
|
find the AI generated docs at https://deepwiki.com/trapexit/mergerfs
|
||||||
|
interesting or useful.
|
||||||
|
|
|
||||||
|
|
@ -1,15 +1,17 @@
|
||||||
# Tweaking Performance
|
# Tweaking Performance
|
||||||
|
|
||||||
`mergerfs` is effectively a filesystem proxy and therefore its
|
**mergerfs** is effectively a filesystem proxy and therefore its
|
||||||
theoretical max performance is that of the underlying devices
|
theoretical max performance is that of the underlying devices
|
||||||
(ignoring caching performed by the kernel.) However, given it is a
|
(ignoring caching performed by the kernel.) However, given it is a
|
||||||
FUSE based filesystem working from userspace there is an increase in
|
FUSE based filesystem working from userspace and it must combine the
|
||||||
overhead relative to kernel based solutions. That said the performance
|
behavior and information from multiple underlying branches there can
|
||||||
can match the theoretical max but it depends greatly on the system's
|
be an increase in overhead relative to other solutions. That said the
|
||||||
|
performance of certain functions, such as IO, can match the
|
||||||
|
theoretical max but it depends greatly on the system's
|
||||||
configuration. There are many things which can impact
|
configuration. There are many things which can impact
|
||||||
performance. Device speeds and latency, network speeds and latency,
|
performance. Device speeds and latency, network speeds and latency,
|
||||||
concurrency and parallel limits of the hardware, read/write sizes,
|
concurrency and parallel limits of the hardware, read/write sizes, the
|
||||||
etc.
|
number of branches, etc.
|
||||||
|
|
||||||
While some settings can impact performance they are all **functional**
|
While some settings can impact performance they are all **functional**
|
||||||
in nature. Meaning they change mergerfs' behavior in some way. As a
|
in nature. Meaning they change mergerfs' behavior in some way. As a
|
||||||
|
|
@ -27,7 +29,7 @@ before changing them to understand how functionality will change.
|
||||||
* enable [passthrough.io](config/passthrough.md) (likely to have the
|
* enable [passthrough.io](config/passthrough.md) (likely to have the
|
||||||
biggest impact)
|
biggest impact)
|
||||||
* change read or process [thread pools](config/threads.md)
|
* change read or process [thread pools](config/threads.md)
|
||||||
* toggle [func.readdir](config/func_readdir.md)
|
* change [func.readdir](config/func_readdir.md)
|
||||||
* increase [readahead](config/readahead.md): `readahead=1024`
|
* increase [readahead](config/readahead.md): `readahead=1024`
|
||||||
* disable `security-capability` and/or [xattr](config/xattr.md)
|
* disable `security-capability` and/or [xattr](config/xattr.md)
|
||||||
* increase cache timeouts [cache.attr](config/cache.md#cacheattr),
|
* increase cache timeouts [cache.attr](config/cache.md#cacheattr),
|
||||||
|
|
|
||||||
|
|
@ -7,11 +7,13 @@ There are no solutions, only trade-offs.
|
||||||
|
|
||||||
* [https://romanrm.net/mhddfs](https://romanrm.net/mhddfs)
|
* [https://romanrm.net/mhddfs](https://romanrm.net/mhddfs)
|
||||||
|
|
||||||
|
mhddfs is, like mergerfs, a FUSE based filesystem which can pool
|
||||||
|
multiple filesystems together.
|
||||||
|
|
||||||
mhddfs had not been updated in over a decade and has known stability
|
mhddfs had not been updated in over a decade and has known stability
|
||||||
and security issues. mergerfs provides a super set of mhddfs' features
|
and security issues. mergerfs provides a super set of mhddfs' features
|
||||||
and offers better performance. In fact, as of 2020, the author of
|
and offers better performance. As of 2020 the author of mhddfs has
|
||||||
mhddfs has [moved to using
|
[moved to using mergerfs.](https://romanrm.net/mhddfs#update)
|
||||||
mergerfs.](https://romanrm.net/mhddfs#update)
|
|
||||||
|
|
||||||
Below is an example of mhddfs and mergerfs setup to work similarly.
|
Below is an example of mhddfs and mergerfs setup to work similarly.
|
||||||
|
|
||||||
|
|
@ -25,14 +27,18 @@ Below is an example of mhddfs and mergerfs setup to work similarly.
|
||||||
* [https://aufs.sourceforge.net](https://aufs.sourceforge.net)
|
* [https://aufs.sourceforge.net](https://aufs.sourceforge.net)
|
||||||
* [https://en.wikipedia.org/wiki/Aufs](https://en.wikipedia.org/wiki/Aufs)
|
* [https://en.wikipedia.org/wiki/Aufs](https://en.wikipedia.org/wiki/Aufs)
|
||||||
|
|
||||||
|
aufs, another union filesystem, is a kernel based overlay filesystem
|
||||||
|
with basic file creation placement policies.
|
||||||
|
|
||||||
While aufs still is maintained it failed to be included in the
|
While aufs still is maintained it failed to be included in the
|
||||||
mainline kernel and is no longer available in most Linux distros
|
mainline kernel and is no longer available in most Linux distros
|
||||||
making it harder to get installed for the average user.
|
making it harder to get installed for the average user.
|
||||||
|
|
||||||
While aufs can often offer better peak performance due to being
|
While aufs can often offer better peak performance due to being
|
||||||
primarily kernel based, mergerfs provides more configurability and is
|
primarily kernel based (at least when `passthrough.io` is disabled),
|
||||||
generally easier to use. mergerfs however does not offer the overlay /
|
mergerfs provides more configurability and is generally easier to
|
||||||
copy-on-write (CoW) features which aufs has.
|
use. mergerfs however does not offer the overlay / copy-on-write (CoW)
|
||||||
|
features which aufs has.
|
||||||
|
|
||||||
|
|
||||||
## unionfs
|
## unionfs
|
||||||
|
|
@ -40,7 +46,7 @@ copy-on-write (CoW) features which aufs has.
|
||||||
* [https://unionfs.filesystems.org](https://unionfs.filesystems.org)
|
* [https://unionfs.filesystems.org](https://unionfs.filesystems.org)
|
||||||
|
|
||||||
unionfs for Linux is a "stackable unification file system" which
|
unionfs for Linux is a "stackable unification file system" which
|
||||||
functions like many other union filesystems. unionfs has not been
|
functions like many other union filesystems. unionfs is no longer
|
||||||
maintained and was last released for Linux v3.14 back in 2014.
|
maintained and was last released for Linux v3.14 back in 2014.
|
||||||
|
|
||||||
Documentation is sparse so a comparison of features is not possible
|
Documentation is sparse so a comparison of features is not possible
|
||||||
|
|
@ -101,7 +107,7 @@ aggregate their storage. The failure of any one device will have no
|
||||||
impact on the other devices. The downside to mergerfs' technique is
|
impact on the other devices. The downside to mergerfs' technique is
|
||||||
the fact you don't actually have contiguous space as large as if you
|
the fact you don't actually have contiguous space as large as if you
|
||||||
used those other technologies. Meaning you can't create a file greater
|
used those other technologies. Meaning you can't create a file greater
|
||||||
than 1TB on a pool of 2 1TB filesystems.
|
than 1TB on a pool of two 1TB filesystems.
|
||||||
|
|
||||||
|
|
||||||
## BTRFS Single Data Profile
|
## BTRFS Single Data Profile
|
||||||
|
|
@ -118,15 +124,20 @@ some abilities to recover data but this is not guaranteed.
|
||||||
* [RAID5](https://en.wikipedia.org/wiki/Standard_RAID_levels#RAID_5)
|
* [RAID5](https://en.wikipedia.org/wiki/Standard_RAID_levels#RAID_5)
|
||||||
* [RAID6](https://en.wikipedia.org/wiki/Standard_RAID_levels#RAID_6)
|
* [RAID6](https://en.wikipedia.org/wiki/Standard_RAID_levels#RAID_6)
|
||||||
|
|
||||||
|
RAID5, RAID6, and similar technologies aggregate multiple devices at
|
||||||
|
the block level and offer 1 or more live parity calculations that can
|
||||||
|
allow the pool to continue to run should 1 device fail and rebuild the
|
||||||
|
data once the device is replaced.
|
||||||
|
|
||||||
mergerfs offers no parity or redundancy features so in that regard the
|
mergerfs offers no parity or redundancy features so in that regard the
|
||||||
technologies are not comparable. [SnapRAID](https://www.snapraid.it)
|
technologies are not comparable. [SnapRAID](https://www.snapraid.it)
|
||||||
can be used in combination with mergerfs to provide redundancy. Unlike
|
or [nonraid](https://github.com/qvr/nonraid) can be used in
|
||||||
traditional RAID5 or RAID6 SnapRAID works with drives of different
|
combination with mergerfs to provide redundancy. Unlike traditional
|
||||||
sizes and can have more than 2 parity drives. However, parity
|
RAID5 or RAID6 SnapRAID works with drives of different sizes and can
|
||||||
calculations are not done in real-time.
|
have more than 2 parity drives. However, parity calculations are not
|
||||||
|
done in real-time. However, nonraid is realtime.
|
||||||
|
|
||||||
See [https://www.snapraid.it/compare](https://www.snapraid.it/compare)
|
For more details and comparison of SnapRAID to related technologies see [https://www.snapraid.it/compare](https://www.snapraid.it/compare).
|
||||||
for more details and comparisons.
|
|
||||||
|
|
||||||
|
|
||||||
## UnRAID
|
## UnRAID
|
||||||
|
|
@ -141,7 +152,9 @@ calculation can have higher peak performance. Some users also prefer
|
||||||
an open source solution.
|
an open source solution.
|
||||||
|
|
||||||
For semi-static data mergerfs + [SnapRAID](http://www.snapraid.it)
|
For semi-static data mergerfs + [SnapRAID](http://www.snapraid.it)
|
||||||
provides a similar, but not real-time, solution.
|
provides a similar, but not real-time, solution. NonRAID (see below)
|
||||||
|
is a fork of UnRAID's parity calculation solution and can also be used
|
||||||
|
with mergerfs.
|
||||||
|
|
||||||
|
|
||||||
## NonRAID
|
## NonRAID
|
||||||
|
|
@ -163,6 +176,9 @@ be used with mergerfs for those looking for a unified view.
|
||||||
|
|
||||||
* [https://en.wikipedia.org/wiki/ZFS](https://en.wikipedia.org/wiki/ZFS)
|
* [https://en.wikipedia.org/wiki/ZFS](https://en.wikipedia.org/wiki/ZFS)
|
||||||
|
|
||||||
|
ZFS is an advanced filesystem with many features including RAID5/6
|
||||||
|
like redundency.
|
||||||
|
|
||||||
mergerfs is very different from ZFS. mergerfs is intended to provide
|
mergerfs is very different from ZFS. mergerfs is intended to provide
|
||||||
flexible pooling of arbitrary filesystems (local or remote), of
|
flexible pooling of arbitrary filesystems (local or remote), of
|
||||||
arbitrary sizes, and arbitrary filesystems. Particularly in `write
|
arbitrary sizes, and arbitrary filesystems. Particularly in `write
|
||||||
|
|
@ -173,6 +189,10 @@ can introduce a number of costs and limitations as described
|
||||||
[here](https://markmcb.com/2020/01/07/five-years-of-btrfs/), and
|
[here](https://markmcb.com/2020/01/07/five-years-of-btrfs/), and
|
||||||
[here](https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNoRealReshaping).
|
[here](https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNoRealReshaping).
|
||||||
|
|
||||||
|
That said given mergerfs' flexibility it is common to see it used in
|
||||||
|
combination with ZFS where critical data is written to a RAIDZ pool
|
||||||
|
and bulk media stored on traditional filesystems pooled via mergerfs.
|
||||||
|
|
||||||
|
|
||||||
## ZFS AnyRAID
|
## ZFS AnyRAID
|
||||||
|
|
||||||
|
|
@ -191,9 +211,9 @@ and there are no timelines or estimates for when it may be released.
|
||||||
|
|
||||||
* [https://stablebit.com](https://stablebit.com)
|
* [https://stablebit.com](https://stablebit.com)
|
||||||
|
|
||||||
DrivePool works only on Windows so not as common an alternative as
|
DrivePool is a commercial filesystem pooling technology for
|
||||||
other Linux solutions. If you want to use Windows then DrivePool is a
|
Windows. If you are looking to use Windows then DrivePool is a good
|
||||||
good option. Functionally the two projects work a bit
|
option. Functionally the two projects work a bit
|
||||||
differently. DrivePool always writes to the filesystem with the most
|
differently. DrivePool always writes to the filesystem with the most
|
||||||
free space and later rebalances. mergerfs does not currently offer
|
free space and later rebalances. mergerfs does not currently offer
|
||||||
rebalance but chooses a branch at file/directory create
|
rebalance but chooses a branch at file/directory create
|
||||||
|
|
@ -202,15 +222,12 @@ and has file pattern matching to further customize the
|
||||||
behavior. mergerfs, not having rebalancing does not have these
|
behavior. mergerfs, not having rebalancing does not have these
|
||||||
features, but similar features are planned for mergerfs v3. DrivePool
|
features, but similar features are planned for mergerfs v3. DrivePool
|
||||||
has builtin file duplication which mergerfs does not natively support
|
has builtin file duplication which mergerfs does not natively support
|
||||||
(but can be done via an external script.)
|
(but can be done via an external program.)
|
||||||
|
|
||||||
There are a lot of misc differences between the two projects but most
|
There are a lot of misc differences between the two projects but most
|
||||||
features in DrivePool can be replicated with external tools in
|
features in DrivePool can be replicated with external tools in
|
||||||
combination with mergerfs.
|
combination with mergerfs.
|
||||||
|
|
||||||
Additionally, DrivePool is a closed source commercial product vs
|
|
||||||
mergerfs a ISC licensed open source project.
|
|
||||||
|
|
||||||
|
|
||||||
## Plan9 binds
|
## Plan9 binds
|
||||||
|
|
||||||
|
|
@ -218,10 +235,10 @@ mergerfs a ISC licensed open source project.
|
||||||
|
|
||||||
Plan9 has the native ability to bind multiple paths/filesystems
|
Plan9 has the native ability to bind multiple paths/filesystems
|
||||||
together to create a setup similar to simplified union
|
together to create a setup similar to simplified union
|
||||||
filesystem. Such bind mounts choose files in a "first found" in the
|
filesystem. Such bind mounts choose files in a "first found" manner
|
||||||
order they are listed similar to mergerfs' `ff` policy. Similar, when
|
based on the order they are configured similar to mergerfs' `ff`
|
||||||
creating a file it will be created on the first directory in the
|
policy. Similarly, when creating a file it will be created on the
|
||||||
union.
|
first directory in the union.
|
||||||
|
|
||||||
Plan 9 isn't a widely used OS so this comparison is mostly academic.
|
Plan 9 isn't a widely used OS so this comparison is mostly academic.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -6,7 +6,7 @@
|
||||||
like something is not explained sufficiently please [file a
|
like something is not explained sufficiently please [file a
|
||||||
ticket.](https://github.com/trapexit/mergerfs/issues)
|
ticket.](https://github.com/trapexit/mergerfs/issues)
|
||||||
* If a `libfuse` argument is not listed it probably shouldn't be used
|
* If a `libfuse` argument is not listed it probably shouldn't be used
|
||||||
and are unsupported.
|
and is unsupported.
|
||||||
* Ensure you're using the latest version. Especially before submitting
|
* Ensure you're using the latest version. Especially before submitting
|
||||||
bug reports.
|
bug reports.
|
||||||
* Run mergerfs as `root`. mergerfs is designed and intended to be run
|
* Run mergerfs as `root`. mergerfs is designed and intended to be run
|
||||||
|
|
@ -15,7 +15,7 @@
|
||||||
seem to skip branches, you get strange permission errors, etc. be
|
seem to skip branches, you get strange permission errors, etc. be
|
||||||
sure the underlying filesystems' permissions are all the same. Use
|
sure the underlying filesystems' permissions are all the same. Use
|
||||||
`mergerfs.fsck` to audit the filesystem for out of sync permissions.
|
`mergerfs.fsck` to audit the filesystem for out of sync permissions.
|
||||||
* If you still have permission issues be sure you are using POSIX ACL
|
* If you still have permission issues be sure you are using POSIX
|
||||||
compliant filesystems. mergerfs doesn't generally make exceptions
|
compliant filesystems. mergerfs doesn't generally make exceptions
|
||||||
for FAT, NTFS, or other non-POSIX filesystem.
|
for FAT, NTFS, or other non-POSIX filesystem.
|
||||||
* Unless using Linux v6.6 or above do **not** use `cache.files=off` if
|
* Unless using Linux v6.6 or above do **not** use `cache.files=off` if
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue