From fc52f89ddce997c371ec12fbbe60997ebb8309cf Mon Sep 17 00:00:00 2001 From: Antonio SJ Musumeci Date: Sat, 18 Aug 2018 22:10:23 -0400 Subject: [PATCH] add FAQ entry on hard links --- README.md | 4 ++++ man/mergerfs.1 | 5 +++++ 2 files changed, 9 insertions(+) diff --git a/README.md b/README.md index b5cebde3..bdfb3012 100644 --- a/README.md +++ b/README.md @@ -624,6 +624,10 @@ MergerFS is **not** an actual filesystem. MergerFS is **not** RAID. It does **no See the previous question's answer. +#### Do hard links work? + +Yes. You need to use `use_ino` to support proper reporting of inodes. Read the section "rename & link" for caveats. + #### Why can't I see my files / directories? It's almost always a permissions issue. Unlike mhddfs, which runs as root and attempts to access content as such, mergerfs always changes it's credentials to that of the caller. This means that if the user doesn't have access to a file or directory than neither will mergerfs. However, because mergerfs is creating a union of paths it may be able to read some files and directories on one drive but not another resulting in an incomplete set. diff --git a/man/mergerfs.1 b/man/mergerfs.1 index c4a238d6..72db7f98 100644 --- a/man/mergerfs.1 +++ b/man/mergerfs.1 @@ -1332,6 +1332,11 @@ It merely shards some \f[B]behavior\f[] and aggregates others. .SS Can mergerfs be removed without affecting the data? .PP See the previous question\[aq]s answer. +.SS Do hard links work? +.PP +Yes. +You need to use \f[C]use_ino\f[] to support proper reporting of inodes. +Read the section "rename & link" for caveats. .SS Why can\[aq]t I see my files / directories? .PP It\[aq]s almost always a permissions issue.