From a13b8225431775cb8333d5820168d91386f0b603 Mon Sep 17 00:00:00 2001 From: Antonio SJ Musumeci Date: Mon, 21 Jan 2019 18:41:19 -0500 Subject: [PATCH] add mention of noforget argument for NFS exports --- README.md | 9 ++++++++- man/mergerfs.1 | 7 +++++++ 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4af3b74a..bf9a588d 100644 --- a/README.md +++ b/README.md @@ -620,6 +620,11 @@ Since enabling `direct_io` disables `mmap` this is not an ideal situation howeve If `direct_io` is disabled it is probably a good idea to enable `dropcacheonclose` to minimize double caching. +#### NFS clients returning ESTALE / Stale file handle + +Be sure to use `noforget` and `use_ino` arguments. + + #### NFS clients don't work Some NFS clients appear to fail when a mergerfs mount is exported. Kodi in particular seems to have issues. @@ -854,7 +859,9 @@ If you don't care about path preservation then simply change the `create` policy #### Can mergerfs mounts be exported over NFS? -Yes. Some clients (Kodi) have issues in which the contents of the NFS mount will not be presented but users have found that enabling the `use_ino` option often fixes that problem. +Yes. Due to current usage of libfuse by mergerfs and how NFS interacts with it it is necessary to add `noforget` to mergerfs options to keep from getting "stale file handle" errors. + +Some clients (Kodi) have issues in which the contents of the NFS mount will not be presented but users have found that enabling the `use_ino` option often fixes that problem. #### Can mergerfs mounts be exported over Samba / SMB? diff --git a/man/mergerfs.1 b/man/mergerfs.1 index dc8669f5..6f869e60 100644 --- a/man/mergerfs.1 +++ b/man/mergerfs.1 @@ -1281,6 +1281,9 @@ ideal situation however write speeds should be increased. .PP If \f[C]direct_io\f[] is disabled it is probably a good idea to enable \f[C]dropcacheonclose\f[] to minimize double caching. +.SS NFS clients returning ESTALE / Stale file handle +.PP +Be sure to use \f[C]noforget\f[] and \f[C]use_ino\f[] arguments. .SS NFS clients don\[aq]t work .PP Some NFS clients appear to fail when a mergerfs mount is exported. @@ -1714,6 +1717,10 @@ Such a setting change will likely occur in mergerfs 3. .SS Can mergerfs mounts be exported over NFS? .PP Yes. +Due to current usage of libfuse by mergerfs and how NFS interacts with +it it is necessary to add \f[C]noforget\f[] to mergerfs options to keep +from getting "stale file handle" errors. +.PP Some clients (Kodi) have issues in which the contents of the NFS mount will not be presented but users have found that enabling the \f[C]use_ino\f[] option often fixes that problem.