From c005463111f3f29169d3b006c063f7335e713dd6 Mon Sep 17 00:00:00 2001 From: Antonio SJ Musumeci Date: Fri, 4 May 2018 09:00:27 -0400 Subject: [PATCH] change examples to use /mnt rather than /tmp --- README.md | 42 +++++++++++++++++++++++------------------- man/mergerfs.1 | 50 +++++++++++++++++++++++++++++--------------------- 2 files changed, 52 insertions(+), 40 deletions(-) diff --git a/README.md b/README.md index 85452f6d..fc939894 100644 --- a/README.md +++ b/README.md @@ -340,30 +340,30 @@ Output: the policy string except for categories where its funcs have multiple ty ##### Example ##### ``` -[trapexit:/tmp/mount] $ xattr -l .mergerfs -user.mergerfs.srcmounts: /tmp/a:/tmp/b +[trapexit:/mnt/mergerfs] $ xattr -l .mergerfs +user.mergerfs.srcmounts: /mnt/a:/mnt/b user.mergerfs.minfreespace: 4294967295 user.mergerfs.moveonenospc: false ... -[trapexit:/tmp/mount] $ xattr -p user.mergerfs.category.search .mergerfs +[trapexit:/mnt/mergerfs] $ xattr -p user.mergerfs.category.search .mergerfs ff -[trapexit:/tmp/mount] $ xattr -w user.mergerfs.category.search newest .mergerfs -[trapexit:/tmp/mount] $ xattr -p user.mergerfs.category.search .mergerfs +[trapexit:/mnt/mergerfs] $ xattr -w user.mergerfs.category.search newest .mergerfs +[trapexit:/mnt/mergerfs] $ xattr -p user.mergerfs.category.search .mergerfs newest -[trapexit:/tmp/mount] $ xattr -w user.mergerfs.srcmounts +/tmp/c .mergerfs -[trapexit:/tmp/mount] $ xattr -p user.mergerfs.srcmounts .mergerfs -/tmp/a:/tmp/b:/tmp/c +[trapexit:/mnt/mergerfs] $ xattr -w user.mergerfs.srcmounts +/mnt/c .mergerfs +[trapexit:/mnt/mergerfs] $ xattr -p user.mergerfs.srcmounts .mergerfs +/mnt/a:/mnt/b:/mnt/c -[trapexit:/tmp/mount] $ xattr -w user.mergerfs.srcmounts =/tmp/c .mergerfs -[trapexit:/tmp/mount] $ xattr -p user.mergerfs.srcmounts .mergerfs -/tmp/c +[trapexit:/mnt/mergerfs] $ xattr -w user.mergerfs.srcmounts =/mnt/c .mergerfs +[trapexit:/mnt/mergerfs] $ xattr -p user.mergerfs.srcmounts .mergerfs +/mnt/c -[trapexit:/tmp/mount] $ xattr -w user.mergerfs.srcmounts '+20 cores. I'm aware of at least a few companies which use mergerfs in production. [Open Media Vault](https://www.openmediavault.org) includes mergerfs is it's sole solution for pooling drives. + #### Can mergerfs be used with drives which already have data / are in use? Yes. MergerFS is a proxy and does **NOT** interfere with the normal form or function of the drives / mounts / paths it manages. diff --git a/man/mergerfs.1 b/man/mergerfs.1 index 872384c1..e07666ac 100644 --- a/man/mergerfs.1 +++ b/man/mergerfs.1 @@ -1,5 +1,5 @@ .\"t -.\" Automatically generated by Pandoc 1.16.0.2 +.\" Automatically generated by Pandoc 1.19.2.4 .\" .TH "mergerfs" "1" "2018\-03\-09" "mergerfs user manual" "" .hy @@ -700,7 +700,7 @@ $\ sudo\ make\ install \f[] .fi .SH RUNTIME -.SS \&.mergerfs pseudo file +.SS .mergerfs pseudo file .IP .nf \f[C] @@ -796,30 +796,30 @@ In that case it will be a comma separated list .IP .nf \f[C] -[trapexit:/tmp/mount]\ $\ xattr\ \-l\ .mergerfs -user.mergerfs.srcmounts:\ /tmp/a:/tmp/b +[trapexit:/mnt/mergerfs]\ $\ xattr\ \-l\ .mergerfs +user.mergerfs.srcmounts:\ /mnt/a:/mnt/b user.mergerfs.minfreespace:\ 4294967295 user.mergerfs.moveonenospc:\ false \&... -[trapexit:/tmp/mount]\ $\ xattr\ \-p\ user.mergerfs.category.search\ .mergerfs +[trapexit:/mnt/mergerfs]\ $\ xattr\ \-p\ user.mergerfs.category.search\ .mergerfs ff -[trapexit:/tmp/mount]\ $\ xattr\ \-w\ user.mergerfs.category.search\ newest\ .mergerfs -[trapexit:/tmp/mount]\ $\ xattr\ \-p\ user.mergerfs.category.search\ .mergerfs +[trapexit:/mnt/mergerfs]\ $\ xattr\ \-w\ user.mergerfs.category.search\ newest\ .mergerfs +[trapexit:/mnt/mergerfs]\ $\ xattr\ \-p\ user.mergerfs.category.search\ .mergerfs newest -[trapexit:/tmp/mount]\ $\ xattr\ \-w\ user.mergerfs.srcmounts\ +/tmp/c\ .mergerfs -[trapexit:/tmp/mount]\ $\ xattr\ \-p\ user.mergerfs.srcmounts\ .mergerfs -/tmp/a:/tmp/b:/tmp/c +[trapexit:/mnt/mergerfs]\ $\ xattr\ \-w\ user.mergerfs.srcmounts\ +/mnt/c\ .mergerfs +[trapexit:/mnt/mergerfs]\ $\ xattr\ \-p\ user.mergerfs.srcmounts\ .mergerfs +/mnt/a:/mnt/b:/mnt/c -[trapexit:/tmp/mount]\ $\ xattr\ \-w\ user.mergerfs.srcmounts\ =/tmp/c\ .mergerfs -[trapexit:/tmp/mount]\ $\ xattr\ \-p\ user.mergerfs.srcmounts\ .mergerfs -/tmp/c +[trapexit:/mnt/mergerfs]\ $\ xattr\ \-w\ user.mergerfs.srcmounts\ =/mnt/c\ .mergerfs +[trapexit:/mnt/mergerfs]\ $\ xattr\ \-p\ user.mergerfs.srcmounts\ .mergerfs +/mnt/c -[trapexit:/tmp/mount]\ $\ xattr\ \-w\ user.mergerfs.srcmounts\ \[aq]+20 cores. +I\[aq]m aware of at least a few companies which use mergerfs in +production. +Open Media Vault (https://www.openmediavault.org) includes mergerfs is +it\[aq]s sole solution for pooling drives. .SS Can mergerfs be used with drives which already have data / are in use? .PP