mirror of
https://github.com/trapexit/mergerfs.git
synced 2025-04-24 22:14:05 +08:00
Misc doc updates + add logo
This commit is contained in:
parent
78fa34098e
commit
9dac54f223
@ -1,9 +1,18 @@
|
||||
# Options
|
||||
|
||||
These options are the same regardless of whether you use them with the
|
||||
`mergerfs` commandline program, in fstab, or in a config file.
|
||||
mergerfs has many options to control it many features. For the average
|
||||
use case the options listed in the [quickstart](../quickstart.md) are
|
||||
sufficient. Most options are related to operating system or filesystem
|
||||
related concepts so having a [basic
|
||||
background](../intro_to_filesystems.md) in such things is recommended
|
||||
for more advanced configurations.
|
||||
|
||||
### types
|
||||
These option names and values are the same regardless of whether you
|
||||
use them with the `mergerfs` commandline program, in fstab, or in a
|
||||
config file.
|
||||
|
||||
|
||||
## types
|
||||
|
||||
- BOOL = 'true' | 'false'
|
||||
- INT = [MIN_INT,MAX_INT]
|
||||
@ -18,7 +27,7 @@ These options are the same regardless of whether you use them with the
|
||||
- POLICY = mergerfs function [policy](functions_categories_policies.md)
|
||||
|
||||
|
||||
### mount options
|
||||
## mount options
|
||||
|
||||
- **config**: Path to a config file. Same arguments as below in
|
||||
key=val / ini style format.
|
||||
|
@ -247,3 +247,13 @@ Be sure to set
|
||||
or use Linux kernel v6.6 or above. rtorrent and some other
|
||||
applications use [mmap](http://linux.die.net/man/2/mmap) to read and
|
||||
write to files and offer no fallback to traditional methods.
|
||||
|
||||
|
||||
## Why don't I see mergerfs options in mount command or /proc/mounts?
|
||||
|
||||
FUSE filesystems, such as mergerfs, are interpreting most of the
|
||||
possible options rather than being given to the kernel where those
|
||||
options in the `mount` command and /proc/mounts come from.
|
||||
|
||||
If you want to see the options of a running instance of mergerfs you
|
||||
can use the [runtime interface](../runtime_interfaces.md).
|
||||
|
Binary file not shown.
Before Width: | Height: | Size: 41 KiB |
BIN
mkdocs/docs/logo.png
Normal file
BIN
mkdocs/docs/logo.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 325 KiB |
@ -101,6 +101,15 @@ used those other technologies. Meaning you can't create a file greater
|
||||
than 1TB on a pool of 2 1TB filesystems.
|
||||
|
||||
|
||||
## BTRFS Single Data Profile
|
||||
|
||||
[BTRFS'](https://btrfs.readthedocs.io) `single` data profile is
|
||||
similar to RAID0 but BTRFS can more explicitly place data and metadata
|
||||
on multiple devices. However, like RAID0 and similar technologies if a
|
||||
single device fails you may lose all data in the pool. BTRFS does have
|
||||
some abilities to recover data but this is not guaranteed.
|
||||
|
||||
|
||||
## RAID5, RAID6
|
||||
|
||||
* [RAID5](https://en.wikipedia.org/wiki/Standard_RAID_levels#RAID_5)
|
||||
|
@ -7,7 +7,7 @@ edit_uri: edit/master/mkdocs/docs/
|
||||
docs_dir: docs
|
||||
theme:
|
||||
name: material
|
||||
logo: logo.jpeg
|
||||
logo: logo.png
|
||||
features:
|
||||
- content.action.edit
|
||||
- content.action.view
|
||||
|
Loading…
x
Reference in New Issue
Block a user