1 .\" Copyright (c) 1989, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)nfsd.8 8.4 (Berkeley) 3/29/95
42 .Op Fl n Ar num_servers
44 .Op Fl p Ar pnfs_setup
45 .Op Fl m Ar mirror_level
46 .Op Fl Fl maxthreads Ar max_threads
47 .Op Fl Fl minthreads Ar min_threads
51 utility runs on a server machine to service
53 requests from client machines.
56 must be running for a machine to operate as a server.
58 Unless otherwise specified, eight servers per CPU for
60 transport are started.
62 The following options are available:
69 without creating any servers.
70 This option can be used along with the
74 options to re-register NFS if the rpcbind server is restarted.
80 without creating any servers.
82 Specifies how many servers to create. This option is equivalent to specifying
86 with their respective arguments to
88 .It Fl Fl maxthreads Ar threads
89 Specifies the maximum servers that will be kept around to service requests.
90 .It Fl Fl minthreads Ar threads
91 Specifies the minimum servers that will be kept around to service requests.
93 Specifies which IP address or hostname to bind to on the local host.
94 This option is recommended when a host has multiple interfaces.
97 options may be specified.
99 Specifies that nfsd should bind to the wildcard IP address.
100 This is the default if no
103 It may also be specified in addition to any
106 Note that NFS/UDP does not operate properly when
107 bound to the wildcard IP address whether you use -a or do not use -h.
108 .It Fl p Ar pnfs_setup
109 Enables pNFS support in the server and specifies the information that the
110 daemon needs to start it.
111 This option can only be used on one server and specifies that this server
112 will be the MetaData Server (MDS) for the pNFS service.
113 This can only be done if there is at least one FreeBSD system configured
114 as a Data Server (DS) for it to use.
118 string is a set of fields separated by ',' characters:
120 Each of these fields specifies one DS.
121 It consists of a server hostname, followed by a ':'
122 and the directory path where the DS's data storage file system is mounted on
124 This can optionally be followed by a '#' and the mds_path, which is the
125 directory path for an exported file system on this MDS.
126 If this is specified, it means that this DS is to be used to store data
127 files for this mds_path file system only.
128 If this optional component does not exist, the DS will be used to store data
129 files for all exported MDS file systems.
130 The DS storage file systems must be mounted on this system before the
132 is started with this option specified.
136 nfsv4-data0:/data0,nfsv4-data1:/data1
138 would specify two DS servers called nfsv4-data0 and nfsv4-data1 that comprise
139 the data storage component of the pNFS service.
140 These two DSs would be used to store data files for all exported file systems
146 are where the data storage servers exported
147 storage directories are mounted on this system (which will act as the MDS).
149 Whereas, for the example:
151 nfsv4-data0:/data0#/export1,nfsv4-data1:/data1#/export2
153 would specify two DSs as above, however nfsv4-data0 will be used to store
156 and nfsv4-data1 will be used to store data files for
160 When using IPv6 addresses for DSs
161 be wary of using link local addresses.
162 The IPv6 address for the DS is sent to the client and there is no scope
164 As such, a link local address may not work for a pNFS client to DS
168 will only use a link local address if it is the only address returned by
171 .It Fl m Ar mirror_level
172 This option is only meaningful when used with the
177 which defines how many of the DSs will
178 have a copy of a file's data storage file.
179 The default of one implies no mirroring of data storage files on the DSs.
182 would normally be set to 2 to enable mirroring, but
183 can be as high as NFSDEV_MAXMIRRORS.
184 There must be at least
186 DSs for each exported file system on the MDS, as specified in the
189 This implies that, for the above example using "#/export1" and "#/export2",
190 mirroring cannot be done.
191 There would need to be two DS entries for each of "#/export1" and "#/export2"
192 in order to support a
196 If mirroring is enabled, the server must use the Flexible File
198 If mirroring is not enabled, the server will use the File layout
199 by default, but this default can be changed to the Flexible File layout if the
201 vfs.nfsd.default_flexfile
212 Ignored; included for backward compatibility.
216 .Dq Li "nfsd -u -t -n 6"
221 transports using six daemons.
223 A server should run enough daemons to handle
224 the maximum level of concurrency from its clients,
225 typically four to six.
229 utility listens for service requests at the port indicated in the
231 server specification; see
232 .%T "Network File System Protocol Specification" ,
234 .%T "NFS: Network File System Version 3 Protocol Specification" ,
236 .%T "Network File System (NFS) Version 4 Protocol" ,
238 .%T "Network File System (NFS) Version 4 Minor Version 1 Protocol" ,
245 is not loaded in the running kernel, it will attempt
246 to load a loadable kernel module containing
254 will exit with an error.
258 is to be run on a host with multiple interfaces or interface aliases, use
261 option is recommended.
262 If you do not use the option NFS may not respond to
263 UDP packets from the same IP address they were sent to.
265 is also recommended when securing NFS exports on a firewalling machine such
266 that the NFS sockets can only be accessed by the inside interface.
270 would then be used to block nfs-related packets that come in on the outside
273 If the server has stopped servicing clients and has generated a console message
275 .Dq Li "nfsd server cache flooded..." ,
276 the value for vfs.nfsd.tcphighwater needs to be increased.
277 This should allow the server to again handle requests without a reboot.
278 Also, you may want to consider decreasing the value for
279 vfs.nfsd.tcpcachetimeo to several minutes (in seconds) instead of 12 hours
282 Unfortunately making vfs.nfsd.tcphighwater too large can result in the mbuf
283 limit being reached, as indicated by a console message
285 .Dq Li "kern.ipc.nmbufs limit reached" .
286 If you cannot find values of the above
288 values that work, you can disable the DRC cache for TCP by setting
289 vfs.nfsd.cachetcp to 0.
293 utility has to be terminated with
295 and cannot be killed with
301 utility needs to ignore these signals in order to stay alive as long
302 as possible during a shutdown, otherwise loopback mounts will
303 not be able to unmount.
307 .Dq Li "kill -USR1 <PID of master nfsd>"
317 .Xr stablerestart 5 ,
328 utility first appeared in
335 is not running, it will service AUTH_SYS requests only. To fix the problem
338 and then restart it, after the
342 If mirroring is enabled via the
344 option and there are Linux clients doing NFSv4.1 mounts, those clients
345 need to be patched to support the
348 the Flexible File layout or the
350 vfs.nfsd.flexlinuxhack
351 must be set to one on the MDS as a workaround.