diff options
author | Nikolaus Rath <Nikolaus@rath.org> | 2016-10-16 15:05:57 -0700 |
---|---|---|
committer | Nikolaus Rath <Nikolaus@rath.org> | 2016-10-16 15:12:29 -0700 |
commit | 1c08ee91f68220c1904efbb278f6641403380474 (patch) | |
tree | 2165ca08360d08c8cc937ef014f5fe47ed2ec623 /doc/README.NFS | |
parent | 199fc0f8335af5487edb243c05a662b60e311463 (diff) |
Various documentation updates
Move README.NFS into doc/
Update project URL
Remove reference to non-existent INSTALL file
Remove outdated/obsolete NEWS and how-fuse-works files.
Update references to examples.
Diffstat (limited to 'doc/README.NFS')
-rw-r--r-- | doc/README.NFS | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/doc/README.NFS b/doc/README.NFS new file mode 100644 index 0000000..f3348d5 --- /dev/null +++ b/doc/README.NFS @@ -0,0 +1,33 @@ +NFS exporting is supported in Linux kernels 2.6.27 or later. + +You need to add an fsid=NNN option to /etc/exports to make exporting a +FUSE directory work. + +Filesystem support +------------------ + +NFS exporting works to some extent on all fuse filesystems, but not +perfectly. This is due to the stateless nature of the protocol, the +server has no way of knowing whether the client is keeping a reference +to a file or not, and hence that file may be removed from the server's +cache. In that case there has to be a way to look up that object +using the inode number, otherwise an ESTALE error will be returned. + +1) low-level interface + +Filesystems need to implement special lookups for the names "." and +"..". The former may be requested on any inode, including +non-directories, while the latter is only requested for directories. +Otherwise these special lookups should behave identically to ordinary +lookups. + +2) high-level interface + +Because the high-level interface is path based, it is not possible to +delegate looking up by inode to the filesystem. + +To work around this, currently a "noforget" option is provided, which +makes the library remember nodes forever. This will make the NFS +server happy, but also results in an ever growing memory footprint for +the filesystem. For this reason if the filesystem is large (or the +memory is small), then this option is not recommended. |