diff --git a/mkdocs/docs/config/options.md b/mkdocs/docs/config/options.md index 32b33597..daeb0938 100644 --- a/mkdocs/docs/config/options.md +++ b/mkdocs/docs/config/options.md @@ -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. diff --git a/mkdocs/docs/faq/why_isnt_it_working.md b/mkdocs/docs/faq/why_isnt_it_working.md index 581d3a9d..77bd454a 100644 --- a/mkdocs/docs/faq/why_isnt_it_working.md +++ b/mkdocs/docs/faq/why_isnt_it_working.md @@ -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). diff --git a/mkdocs/docs/logo.jpeg b/mkdocs/docs/logo.jpeg deleted file mode 100644 index 5f0c6129..00000000 Binary files a/mkdocs/docs/logo.jpeg and /dev/null differ diff --git a/mkdocs/docs/logo.png b/mkdocs/docs/logo.png new file mode 100644 index 00000000..dda524fc Binary files /dev/null and b/mkdocs/docs/logo.png differ diff --git a/mkdocs/docs/project_comparisons.md b/mkdocs/docs/project_comparisons.md index f4a99c73..9d865628 100644 --- a/mkdocs/docs/project_comparisons.md +++ b/mkdocs/docs/project_comparisons.md @@ -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) diff --git a/mkdocs/mkdocs.yml b/mkdocs/mkdocs.yml index f9a996e0..07e9abdd 100644 --- a/mkdocs/mkdocs.yml +++ b/mkdocs/mkdocs.yml @@ -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