Mirror
/
mergerfs
mirror of https://github.com/trapexit/mergerfs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Merge pull request #564 from trapexit/nfs 

add mention of noforget argument for NFS exports
pull/565/head
trapexit 6 years ago
committed by GitHub
parent
40319081e0 a13b822543
commit
8e0aa1d9a6
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 15 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 9
      README.md
  2. 7
      man/mergerfs.1

9
README.md
View File

@ -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. 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 #### NFS clients don't work
Some NFS clients appear to fail when a mergerfs mount is exported. Kodi in particular seems to have issues. 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? #### 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? #### Can mergerfs mounts be exported over Samba / SMB?

7
man/mergerfs.1
View File

@ -1281,6 +1281,9 @@ ideal situation however write speeds should be increased.
.PP .PP
If \f[C]direct_io\f[] is disabled it is probably a good idea to enable If \f[C]direct_io\f[] is disabled it is probably a good idea to enable
\f[C]dropcacheonclose\f[] to minimize double caching. \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 .SS NFS clients don\[aq]t work
.PP .PP
Some NFS clients appear to fail when a mergerfs mount is exported. 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? .SS Can mergerfs mounts be exported over NFS?
.PP .PP
Yes. 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 Some clients (Kodi) have issues in which the contents of the NFS mount
will not be presented but users have found that enabling the will not be presented but users have found that enabling the
\f[C]use_ino\f[] option often fixes that problem. \f[C]use_ino\f[] option often fixes that problem.

Write Preview
Loading…
Cancel
Save