diff --git a/man/mergerfs.1 b/man/mergerfs.1 index 52b3a6a0..68e93fcc 100644 --- a/man/mergerfs.1 +++ b/man/mergerfs.1 @@ -287,7 +287,8 @@ same as \f[C]mv\f[] would). Such apps include: gvfsd\-fuse v1.20.3 and prior, Finder / CIFS/SMB client in Apple OSX 10.9+, NZBGet, Samba\[aq]s recycling bin feature. .IP \[bu] 2 -If using a policy which tries to preserve directories (epmfs,eplfs) +If using a \f[C]create\f[] policy which tries to preserve directory +paths (epmfs,eplfs) .IP \[bu] 2 Using the \f[C]rename\f[] policy get the list of files to rename .IP \[bu] 2 @@ -316,7 +317,8 @@ Remove the target from all drives with no source file Remove the source from all drives which failed to rename .RE .IP \[bu] 2 -If using a policy which does \f[B]not\f[] try to preserve directories +If using a \f[C]create\f[] policy which does \f[B]not\f[] try to +preserve directory paths .IP \[bu] 2 Using the \f[C]rename\f[] policy get the list of files to rename .IP \[bu] 2 @@ -585,19 +587,22 @@ A\ B\ C Find tooling to help with managing \f[C]mergerfs\f[] at: https://github.com/trapexit/mergerfs\-tools .IP \[bu] 2 -fsck.mergerfs: Provides permissions and ownership auditing and the +mergerfs.fsck: Provides permissions and ownership auditing and the ability to fix them .IP \[bu] 2 mergerfs.mktrash: Creates FreeDesktop.org Trash specification compatible directories on a mergerfs mount .SH TIPS / NOTES .IP \[bu] 2 +Detailed guides to setting up a backup solution using mergerfs and other +technologies: https://github.com/trapexit/backup\-and\-recovery\-howtos +.IP \[bu] 2 If you don\[aq]t see some directories / files you expect in a merged point be sure the user has permission to all the underlying directories. If \f[C]/drive0/a\f[] has is owned by \f[C]root:root\f[] with ACLs set to \f[C]0700\f[] and \f[C]/drive1/a\f[] is \f[C]root:root\f[] and \f[C]0755\f[] you\[aq]ll see only \f[C]/drive1/a\f[]. -Use \f[C]fsck.mergerfs\f[] to audit the drive for out of sync +Use \f[C]mergerfs.fsck\f[] to audit the drive for out of sync permissions. .IP \[bu] 2 Since POSIX gives you only error or success on calls its difficult to @@ -790,7 +795,7 @@ behavior poses a problem. \f[B]libfuse\f[] is multithreaded by default. We\[aq]d need to lock access to \f[B]seteuid\f[] and \f[B]setegid\f[] with a mutex so that the several threads aren\[aq]t stepping on one -another and files end up with weird permissions and ownership. +anofther and files end up with weird permissions and ownership. This however wouldn\[aq]t scale well. With lots of calls the contention on that mutex would be extremely high. Thankfully on Linux and OSX we have a better solution.