You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

33 lines
1.3 KiB

  1. NFS exporting is supported in Linux kernels 2.6.27 or later.
  2. You need to add an fsid=NNN option to /etc/exports to make exporting a
  3. FUSE directory work.
  4. Filesystem support
  5. ------------------
  6. NFS exporting works to some extent on all fuse filesystems, but not
  7. perfectly. This is due to the stateless nature of the protocol, the
  8. server has no way of knowing whether the client is keeping a reference
  9. to a file or not, and hence that file may be removed from the server's
  10. cache. In that case there has to be a way to look up that object
  11. using the inode number, otherwise an ESTALE error will be returned.
  12. 1) low-level interface
  13. Filesystems need to implement special lookups for the names "." and
  14. "..". The former may be requested on any inode, including
  15. non-directories, while the latter is only requested for directories.
  16. Otherwise these special lookups should behave identically to ordinary
  17. lookups.
  18. 2) high-level interface
  19. Because the high-level interface is path based, it is not possible to
  20. delegate looking up by inode to the filesystem.
  21. To work around this, currently a "noforget" option is provided, which
  22. makes the library remember nodes forever. This will make the NFS
  23. server happy, but also results in an ever growing memory footprint for
  24. the filesystem. For this reason if the filesystem is large (or the
  25. memory is small), then this option is not recommended.