{"id":3855,"date":"2022-12-20T17:20:16","date_gmt":"2022-12-20T20:20:16","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/exportfs-man8\/"},"modified":"2022-12-20T17:20:16","modified_gmt":"2022-12-20T20:20:16","slug":"exportfs-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/exportfs-man8\/","title":{"rendered":"exportfs (man8)"},"content":{"rendered":"

exportfs<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
CONFIGURATION FILE<\/a>
DISCUSSION<\/a>
EXAMPLES<\/a>
USAGE NOTES<\/a>
FILES<\/a>
SEE ALSO<\/a>
AUTHORS<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

exportfs \u2212 maintain table of exported NFS file systems<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

\/usr\/sbin\/exportfs [-avi] [-o<\/b> options,..<\/i>] [<\/b>client:\/path<\/i> ..]
\/usr\/sbin\/exportfs -r [-v]
\/usr\/sbin\/exportfs [-av] -u [<\/b>client:\/path<\/i> ..]
\/usr\/sbin\/exportfs [-v]
\/usr\/sbin\/exportfs -f
\/usr\/sbin\/exportfs -s<\/b><\/p>\n

DESCRIPTION <\/a> <\/h2>\n

An NFS server maintains a table of local physical file systems that are accessible to NFS clients. Each file system in this table is referred to as an exported file system<\/i>, or export<\/i>, for short.<\/p>\n

The exportfs<\/b> command maintains the current table of exports for the NFS server. The master export table is kept in a file named \/var\/lib\/nfs\/etab<\/i>. This file is read by rpc.mountd<\/b> when a client sends an NFS MOUNT request.<\/p>\n

Normally the master export table is initialized with the contents of \/etc\/exports<\/i> and files under \/etc\/exports.d<\/i> by invoking exportfs -a<\/b>. However, a system administrator can choose to add or delete exports without modifying \/etc\/exports<\/i> or files under \/etc\/exports.d<\/i> by using the exportfs<\/b> command.<\/p>\n

exportfs<\/b> and its partner program rpc.mountd<\/b> work in one of two modes: a legacy mode which applies to 2.4 and earlier versions of the Linux kernel, and a new mode which applies to 2.6 and later versions, providing the nfsd<\/b> virtual filesystem has been mounted at \/proc\/fs\/nfsd<\/i> or \/proc\/fs\/nfs<\/i>. On 2.6 kernels, if this filesystem is not mounted, the legacy mode is used.<\/p>\n

In the new mode, exportfs<\/b> does not give any information to the kernel, but provides it only to rpc.mountd<\/b> through the \/var\/lib\/nfs\/etab<\/i> file. rpc.mountd<\/b> then manages kernel requests for information about exports, as needed.<\/p>\n

In the legacy mode, exports which identify a specific host, rather than a subnet or netgroup, are entered directly into the kernel\u2019s export table, as well as being written to \/var\/lib\/nfs\/etab<\/i>. Further, exports listed in \/var\/lib\/nfs\/rmtab<\/i> which match a non host-specific export request will cause an appropriate export entry for the host given in rmtab<\/i> to be added to the kernel\u2019s export table.<\/p>\n

OPTIONS <\/a> <\/h2>\n

\u2212d kind or \u2212\u2212debug kind<\/b><\/p>\n

Turn on debugging. Valid kinds are: all, auth, call, general and parse. Debugging can also be turned on by setting debug=<\/b> in the [exportfs]<\/b> section of \/etc\/nfs.conf<\/i>.<\/p>\n\n\n
<\/td>\n\n

-a<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Export or unexport all directories.<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

-o<\/b> options,…<\/i><\/p>\n

Specify a list of export options in the same manner as in exports<\/b>(5).<\/p>\n\n\n\n\n\n\n\n
<\/td>\n\n

-i<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Ignore the \/etc\/exports<\/i> file and files under \/etc\/exports.d<\/i> directory. Only default options and options given on the command line are used.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

-r<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Reexport all directories, synchronizing \/var\/lib\/nfs\/etab<\/i> with \/etc\/exports<\/i> and files under \/etc\/exports.d<\/i>. This option removes entries in \/var\/lib\/nfs\/etab<\/i> which have been deleted from \/etc\/exports<\/i> or files under \/etc\/exports.d<\/i>, and removes any entries from the kernel export table which are no longer valid.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

-u<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Unexport one or more directories.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

-f<\/b><\/p>\n<\/td>\n

<\/td>\n\n

If \/proc\/fs\/nfsd<\/i> or \/proc\/fs\/nfs<\/i> is mounted, flush everything out of the kernel\u2019s export table. Fresh entries for active clients are added to the kernel\u2019s export table by rpc.mountd<\/b> when they make their next NFS mount request.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

-v<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Be verbose. When exporting or unexporting, show what\u2019s going on. When displaying the current export list, also display the list of export options.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

-s<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Display the current export list suitable for \/etc\/exports.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

CONFIGURATION FILE <\/a> <\/h2>\n

The [exportfs]<\/b> section of the \/etc\/nfs.conf<\/i> configuration file can contain a debug<\/b> value, which can be one or more from the list general<\/b>, call<\/b>, auth<\/b>, parse<\/b>, all<\/b>. When a list is given, the members should be comma-separated.<\/p>\n

exportfs<\/b> will also recognize the state-directory-path<\/b> value from the [mountd]<\/b> section.<\/p>\n

DISCUSSION <\/a> <\/h2>\n

Exporting Directories<\/b>
The first synopsis shows how to invoke exportfs<\/b> when adding new entries to the export table. When using exportfs -a<\/b>, all exports listed in \/etc\/exports<\/i> and files under \/etc\/exports.d<\/i> are added to \/var\/lib\/nfs\/etab<\/i>. The kernel\u2019s export table is also updated as needed.<\/p>\n

The host:\/path<\/i> argument specifies a local directory to export, along with the client or clients who are permitted to access it. See exports(5)<\/b> for a description of supported options and access list formats.<\/p>\n

IPv6 presentation addresses contain colons, which are already used to separate the “host” and “path” command line arguments. When specifying a client using a raw IPv6 address, enclose the address in square brackets. For IPv6 network addresses, place the prefix just after the closing bracket.<\/p>\n

To export a directory to the world, simply specify :\/path<\/i>.<\/p>\n

The export options for a particular host\/directory pair derive from several sources. The default export options are sync,ro,root_squash,wdelay<\/b>. These can be overridden by entries in \/etc\/exports<\/i> or files under \/etc\/exports.d<\/i>.<\/p>\n

A system administrator may override options from these sources using the -o<\/b> command-line option on exportfs<\/b>. This option takes a comma-separated list of options in the same fashion as one would specify them in \/etc\/exports<\/i>. In this way exportfs<\/b> can be used to modify the export options of an already exported directory.<\/p>\n

Unexporting Directories<\/b>
The third synopsis shows how to unexport a currently exported directory. When using exportfs -ua<\/b>, all entries listed in \/var\/lib\/nfs\/etab<\/i> are removed from the kernel export tables, and the file is cleared. This effectively shuts down all NFS activity.<\/p>\n

To remove an export, specify a host:\/path<\/i> pair. This deletes the specified entry from \/var\/lib\/nfs\/etab<\/i> and removes the corresponding kernel entry (if any).<\/p>\n

Dumping the Export Table<\/b>
Invoking exportfs<\/b> without options shows the current list of exported file systems. Adding the -v<\/b> option causes exportfs<\/b> to display the export options for each export.<\/p>\n

EXAMPLES <\/a> <\/h2>\n

The following adds all directories listed in \/etc\/exports<\/i> and files under \/etc\/exports.d<\/i> to \/var\/lib\/nfs\/etab<\/i> and pushes the resulting export entries into the kernel:<\/p>\n

# exportfs -a<\/b><\/p>\n

To export the \/usr\/tmp<\/i> directory to host django<\/b>, allowing insecure file locking requests from clients:<\/p>\n

# exportfs -o insecure_locks django:\/usr\/tmp<\/b><\/p>\n

To unexport the \/usr\/tmp<\/i> directory:<\/p>\n

# exportfs -u django:\/usr\/tmp<\/b><\/p>\n

To unexport all exports listed in \/etc\/exports<\/i> and files under \/etc\/exports.d<\/i>:<\/p>\n

# exportfs -au<\/b><\/p>\n

To export the \/usr\/tmp<\/i> directory to IPv6 link-local clients:<\/p>\n

# exportfs [fe80::]\/64:\/usr\/tmp<\/b><\/p>\n

USAGE NOTES <\/a> <\/h2>\n

Exporting to IP networks or DNS and NIS domains does not enable clients from these groups to access NFS immediately. Rather, these sorts of exports are hints to rpc.mountd<\/b>(8) to grant any mount requests from these clients. This is usually not a problem, because any existing mounts are preserved in rmtab<\/i> across reboots.<\/p>\n

When unexporting a network or domain entry, any current exports to members of this group will be checked against the remaining valid exports and if they themselves are no longer valid they will be removed.<\/p>\n

FILES <\/a> <\/h2>\n\n\n\n\n\n
<\/td>\n\n

\/etc\/exports<\/i><\/p>\n<\/td>\n

<\/td>\n\n

input file listing exports, export options, and access control lists<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\/etc\/exports.d<\/i><\/p>\n<\/td>\n

<\/td>\n\n

directory where extra input files are stored. Note:<\/b> only files that end with .exports<\/i> are used.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\/var\/lib\/nfs\/etab<\/i><\/p>\n<\/td>\n

<\/td>\n\n

master table of exports<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\/var\/lib\/nfs\/rmtab<\/i><\/p>\n<\/td>\n

<\/td>\n\n

table of clients accessing server\u2019s exports<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

SEE ALSO <\/a> <\/h2>\n

exports<\/b>(5), nfs.conf<\/b>(5), rpc.mountd<\/b>(8), netgroup<\/b>(5)<\/p>\n

AUTHORS <\/a> <\/h2>\n

Olaf Kirch
Neil Brown <\/p>\n

\n","protected":false},"excerpt":{"rendered":"

exportfs \u2212 maintain table of exported NFS file systems <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,948,4],"class_list":["post-3855","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-exportfs","tag-man8"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3855","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3855"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3855\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3855"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3855"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3855"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}