"Fossies" - the Fresh Open Source Software Archive

Member "fuse-3.2.1/doc/README.NFS" (14 Nov 2017, 1429 Bytes) of package /linux/misc/fuse-3.2.1.tar.xz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

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