filesystems/nfs/exporting.rst

9 All filesystem operations require a dentry (or two) as a starting
12 applications that access a filesystem via a remote filesystem protocol
19 The mechanism discussed here allows each filesystem implementation to
20 specify how to generate an opaque (outside of the filesystem) byte
26 A filesystem which supports the mapping between filehandle fragments
34 The dcache normally contains a proper prefix of any given filesystem
35 tree.  This means that if any filesystem object is in the dcache, then
36 all of the ancestors of that filesystem object are also in the dcache.
44 the dcache that are not needed for normal filesystem access.
98 Filesystem Issues
101 For a filesystem to be exportable it must:
120 A file system implementation declares that instances of the filesystem
157     filesystem to communicate such information to nfsd. See the Export
172 contains a "flags" field that allows the filesystem to communicate to nfsd
176   EXPORT_OP_NOWCC - disable NFSv3 WCC attributes on this filesystem
186     replies when doing operations on this filesystem. Consider enabling
194     export consists of an entire filesystem, this is trivial. nfsd can just
195     ensure that the filehandle live on the filesystem. When only part of a
196     filesystem is exported however, then nfsd must walk the ancestors of the
199     This flag exempts the filesystem from subtree checking and causes
216   EXPORT_OP_REMOTE_FS - Backing storage for this filesystem is remote
226   EXPORT_OP_NOATOMIC_ATTR - Filesystem does not update attributes atomically
227     EXPORT_OP_NOATOMIC_ATTR indicates that the exported filesystem
234   EXPORT_OP_FLUSH_ON_CLOSE - Filesystem flushes file data on close(2)
242   EXPORT_OP_ASYNC_LOCK - Indicates a capable filesystem to do async lock
243     requests from lockd. Only set EXPORT_OP_ASYNC_LOCK if the filesystem has