1.\" Copyright (c) 1992, 1993, 1994, 1995 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 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.\" 4. 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. 15.\" 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 26.\" SUCH DAMAGE. 27.\" 28.\" @(#)mount_nfs.8 8.3 (Berkeley) 3/29/95 29.\" $FreeBSD$ 30.\" 31.Dd July 8, 2013 32.Dt MOUNT_NFS 8 33.Os 34.Sh NAME 35.Nm mount_nfs 36.Nd mount NFS file systems 37.Sh SYNOPSIS 38.Nm 39.Op Fl 23bcdiLlNPsTU 40.Op Fl a Ar maxreadahead 41.Op Fl D Ar deadthresh 42.Op Fl g Ar maxgroups 43.Op Fl I Ar readdirsize 44.Op Fl o Ar options 45.Op Fl R Ar retrycnt 46.Op Fl r Ar readsize 47.Op Fl t Ar timeout 48.Op Fl w Ar writesize 49.Op Fl x Ar retrans 50.Ar rhost : Ns Ar path node 51.Sh DESCRIPTION 52The 53.Nm 54utility calls the 55.Xr nmount 2 56system call to prepare and graft a remote NFS file system 57.Pq Ar rhost : Ns Ar path 58on to the file system tree at the point 59.Ar node . 60This command is normally executed by 61.Xr mount 8 . 62It implements the mount protocol as described in RFC 1094, Appendix A and 63.%T "NFS: Network File System Version 3 Protocol Specification" , 64Appendix I. 65.Pp 66If the file system type is specified as ``oldnfs'', which implies this 67command is run as ``mount_oldnfs'', then it forces use of the old NFS 68client, which does not support the 69.Cm nfsv4 70option. 71.Pp 72By default, 73.Nm 74keeps retrying until the mount succeeds. 75This behaviour is intended for file systems listed in 76.Xr fstab 5 77that are critical to the boot process. 78For non-critical file systems, the 79.Cm bg 80and 81.Cm retrycnt 82options provide mechanisms to prevent the boot process from hanging 83if the server is unavailable. 84.Pp 85If the server becomes unresponsive while an NFS file system is 86mounted, any new or outstanding file operations on that file system 87will hang uninterruptibly until the server comes back. 88To modify this default behaviour, see the 89.Cm intr 90and 91.Cm soft 92options. 93.Pp 94The options are: 95.Bl -tag -width indent 96.It Fl o 97Options are specified with a 98.Fl o 99flag followed by a comma separated string of options. 100See the 101.Xr mount 8 102man page for possible options and their meanings. 103The following NFS specific options are also available: 104.Bl -tag -width indent 105.It Cm acregmin Ns = Ns Aq Ar seconds 106.It Cm acregmax Ns = Ns Aq Ar seconds 107.It Cm acdirmin Ns = Ns Aq Ar seconds 108.It Cm acdirmax Ns = Ns Aq Ar seconds 109When attributes of files are cached, a timeout calculated to determine 110whether a given cache entry has expired. 111These four values determine the upper and lower bounds of the timeouts for 112.Dq directory 113attributes and 114.Dq regular 115(ie: everything else). 116The default values are 3 -> 60 seconds 117for regular files, and 30 -> 60 seconds for directories. 118The algorithm to calculate the timeout is based on the age of the file. 119The older the file, 120the longer the cache is considered valid, subject to the limits above. 121.It Cm allgssname 122This option can be used along with 123.Fl o Cm gssname 124to specify that all operations should use the host-based initiator 125credential. 126This may be used for clients that run system daemons that need to 127access files on the NFSv4 mounted volume. 128.It Cm bg 129If an initial attempt to contact the server fails, fork off a child to keep 130trying the mount in the background. 131Useful for 132.Xr fstab 5 , 133where the file system mount is not critical to multiuser operation. 134.It Cm deadthresh Ns = Ns Aq Ar value 135Set the 136.Dq "dead server threshold" 137to the specified number of round trip timeout intervals before a 138.Dq "server not responding" 139message is displayed. 140.It Cm dumbtimer 141Turn off the dynamic retransmit timeout estimator. 142This may be useful for UDP mounts that exhibit high retry rates, 143since it is possible that the dynamically estimated timeout interval is too 144short. 145.It Cm fg 146Same as not specifying 147.Cm bg . 148.It Cm gssname Ns = Ns Aq Ar service-principal-name 149This option can be used with the KerberosV security flavors for NFSv4 mounts 150to specify the 151.Dq "service-principal-name" 152of a host-based entry in the default 153keytab file that is used for system operations. 154It allows the mount to be performed by 155.Dq "root" 156and avoids problems with 157cached credentials for the system operations expiring. 158The 159.Dq "service-prinicpal-name" 160should be specified without instance or domain and is typically 161.Dq "host" , 162.Dq "nfs" 163or 164.Dq "root" . 165.It Cm hard 166Same as not specifying 167.Cm soft . 168.It Cm intr 169Make the mount interruptible, which implies that file system calls that 170are delayed due to an unresponsive server will fail with EINTR when a 171termination signal is posted for the process. 172.It Cm maxgroups Ns = Ns Aq Ar value 173Set the maximum size of the group list for the credentials to the 174specified value. 175This should be used for mounts on old servers that cannot handle a 176group list size of 16, as specified in RFC 1057. 177Try 8, if users in a lot of groups cannot get response from the mount 178point. 179.It Cm mntudp 180Force the mount protocol to use UDP transport, even for TCP NFS mounts. 181(Necessary for some old 182.Bx 183servers.) 184.It Cm nametimeo Ns = Ns Aq Ar value 185Override the default of NFS_DEFAULT_NAMETIMEO for the timeout (in seconds) 186for positive name cache entries. 187If this is set to 0 it disables positive name caching for the mount point. 188.It Cm negnametimeo Ns = Ns Aq Ar value 189Override the default of NFS_DEFAULT_NEGNAMETIMEO for the timeout (in seconds) 190for negative name cache entries. If this is set to 0 it disables negative 191name caching for the mount point. 192.It Cm nfsv2 193Use the NFS Version 2 protocol (the default is to try version 3 first 194then version 2). 195Note that NFS version 2 has a file size limit of 2 gigabytes. 196.It Cm nfsv3 197Use the NFS Version 3 protocol. 198.It Cm nfsv4 199Use the NFS Version 4 protocol. 200This option will force the mount to use 201TCP transport. 202.It Cm minorversion Ns = Ns Aq Ar value 203Override the default of 0 for the minor version of the NFS Version 4 protocol. 204The only minor version currently supported is 1. 205This option is only meaningful when used with the 206.Cm nfsv4 207option. 208.It Cm pnfs 209Enable support for parallel NFS (pNFS) for minor version 1 of the 210NFS Version 4 protocol. 211This option is only meaningful when used with the 212.Cm minorversion 213option. 214.It Cm noconn 215For UDP mount points, do not do a 216.Xr connect 2 . 217This must be used if the server does not reply to requests from the standard 218NFS port number 2049 or replies to requests using a different IP address 219(which can occur if the server is multi-homed). 220Setting the 221.Va vfs.nfs.nfs_ip_paranoia 222sysctl to 0 will make this option the default. 223.It Cm nocto 224Normally, NFS clients maintain the close-to-open cache coherency. 225This works by flushing at close time and checking at open time. 226Checking at open time is implemented by getting attributes from 227the server and purging the data cache if they do not match 228attributes cached by the client. 229.Pp 230This option disables checking at open time. 231It may improve performance for read-only mounts, 232but should only be used if the data on the server changes rarely. 233Be sure to understand the consequences before enabling this option. 234.It Cm noinet4 , noinet6 235Disables 236.Dv AF_INET 237or 238.Dv AF_INET6 239connections. 240Useful for hosts that have 241both an A record and an AAAA record for the same name. 242.It Cm nolockd 243Do 244.Em not 245forward 246.Xr fcntl 2 247locks over the wire. 248All locks will be local and not seen by the server 249and likewise not seen by other NFS clients. 250This removes the need to run the 251.Xr rpcbind 8 252service and the 253.Xr rpc.statd 8 254and 255.Xr rpc.lockd 8 256servers on the client. 257Note that this option will only be honored when performing the 258initial mount, it will be silently ignored if used while updating 259the mount options. 260.It Cm principal 261For the RPCSEC_GSS security flavors, such as krb5, krb5i and krb5p, 262this option sets the name of the host based principal name expected 263by the server. This option overrides the default, which will be 264``nfs@<server-fqdn>'' and should normally be sufficient. 265.It Cm noresvport 266Do 267.Em not 268use a reserved socket port number (see below). 269.It Cm port Ns = Ns Aq Ar port_number 270Use specified port number for NFS requests. 271The default is to query the portmapper for the NFS port. 272.It Cm rdirplus 273Used with NFSV3 to specify that the \fBReaddirPlus\fR RPC should 274be used. 275For NFSV4, setting this option has a similar effect, in that it will make 276the Readdir Operation get more attributes. 277This option reduces RPC traffic for cases such as 278.Dq "ls -l" , 279but tends to flood the attribute and name caches with prefetched entries. 280Try this option and see whether performance improves or degrades. 281Probably 282most useful for client to server network interconnects with a large bandwidth 283times delay product. 284.It Cm readahead Ns = Ns Aq Ar value 285Set the read-ahead count to the specified value. 286This may be in the range of 0 - 4, and determines how many blocks 287will be read ahead when a large file is being read sequentially. 288Trying a value greater than 1 for this is suggested for 289mounts with a large bandwidth * delay product. 290.It Cm readdirsize Ns = Ns Aq Ar value 291Set the readdir read size to the specified value. 292The value should normally 293be a multiple of 294.Dv DIRBLKSIZ 295that is <= the read size for the mount. 296.It Cm resvport 297Use a reserved socket port number. 298This flag is obsolete, and only retained for compatibility reasons. 299Reserved port numbers are used by default now. 300(For the rare case where the client has a trusted root account 301but untrustworthy users and the network cables are in secure areas this does 302help, but for normal desktop clients this does not apply.) 303.It Cm retrans Ns = Ns Aq Ar value 304Set the retransmit timeout count for soft mounts to the specified value. 305.It Cm retrycnt Ns = Ns Aq Ar count 306Set the mount retry count to the specified value. 307The default is a retry count of zero, which means to keep retrying 308forever. 309There is a 60 second delay between each attempt. 310.It Cm rsize Ns = Ns Aq Ar value 311Set the read data size to the specified value. 312It should normally be a power of 2 greater than or equal to 1024. 313This should be used for UDP mounts when the 314.Dq "fragments dropped due to timeout" 315value is getting large while actively using a mount point. 316(Use 317.Xr netstat 1 318with the 319.Fl s 320option to see what the 321.Dq "fragments dropped due to timeout" 322value is.) 323.It Cm sec Ns = Ns Aq Ar flavor 324This option specifies what security flavor should be used for the mount. 325Currently, they are: 326.Bd -literal 327krb5 - Use KerberosV authentication 328krb5i - Use KerberosV authentication and 329 apply integrity checksums to RPCs 330krb5p - Use KerberosV authentication and 331 encrypt the RPC data 332sys - The default AUTH_SYS, which uses a 333 uid + gid list authenticator 334.Ed 335.It Cm soft 336A soft mount, which implies that file system calls will fail 337after 338.Ar retrycnt 339round trip timeout intervals. 340.It Cm tcp 341Use TCP transport. 342This is the default option, as it provides for increased reliability on both 343LAN and WAN configurations compared to UDP. 344Some old NFS servers do not support this method; UDP mounts may be required 345for interoperability. 346.It Cm timeout Ns = Ns Aq Ar value 347Set the initial retransmit timeout to the specified value. 348May be useful for fine tuning UDP mounts over internetworks 349with high packet loss rates or an overloaded server. 350Try increasing the interval if 351.Xr nfsstat 1 352shows high retransmit rates while the file system is active or reducing the 353value if there is a low retransmit rate but long response delay observed. 354(Normally, the 355.Cm dumbtimer 356option should be specified when using this option to manually 357tune the timeout 358interval.) 359.It Cm udp 360Use UDP transport. 361.It Cm wcommitsize Ns = Ns Aq Ar value 362Set the maximum pending write commit size to the specified value. 363This determines the maximum amount of pending write data that the NFS 364client is willing to cache for each file. 365.It Cm wsize Ns = Ns Aq Ar value 366Set the write data size to the specified value. 367Ditto the comments w.r.t.\& the 368.Cm rsize 369option, but using the 370.Dq "fragments dropped due to timeout" 371value on the server instead of the client. 372Note that both the 373.Cm rsize 374and 375.Cm wsize 376options should only be used as a last ditch effort at improving performance 377when mounting servers that do not support TCP mounts. 378.El 379.El 380.Sh COMPATIBILITY 381The following command line flags are equivalent to 382.Fl o 383named options and are supported for compatibility with older 384installations. 385.Bl -tag -width indent 386.It Fl 2 387Same as 388.Fl o Cm nfsv2 389.It Fl 3 390Same as 391.Fl o Cm nfsv3 392.It Fl D 393Same as 394.Fl o Cm deadthresh 395.It Fl I 396Same as 397.Fl o Cm readdirsize Ns = Ns Aq Ar value 398.It Fl L 399Same as 400.Fl o Cm nolockd 401.It Fl N 402Same as 403.Fl o Cm noresvport 404.It Fl P 405Use a reserved socket port number. 406This flag is obsolete, and only retained for compatibility reasons. 407(For the rare case where the client has a trusted root account 408but untrustworthy users and the network cables are in secure areas this does 409help, but for normal desktop clients this does not apply.) 410.It Fl R 411Same as 412.Fl o Cm retrycnt Ns = Ns Aq Ar value 413.It Fl T 414Same as 415.Fl o Cm tcp 416.It Fl U 417Same as 418.Fl o Cm mntudp 419.It Fl a 420Same as 421.Fl o Cm readahead Ns = Ns Aq Ar value 422.It Fl b 423Same as 424.Fl o Cm bg 425.It Fl c 426Same as 427.Fl o Cm noconn 428.It Fl d 429Same as 430.Fl o Cm dumbtimer 431.It Fl g 432Same as 433.Fl o Cm maxgroups 434.It Fl i 435Same as 436.Fl o Cm intr 437.It Fl l 438Same as 439.Fl o Cm rdirplus 440.It Fl r 441Same as 442.Fl o Cm rsize Ns = Ns Aq Ar value 443.It Fl s 444Same as 445.Fl o Cm soft 446.It Fl t 447Same as 448.Fl o Cm retransmit Ns = Ns Aq Ar value 449.It Fl w 450Same as 451.Fl o Cm wsize Ns = Ns Aq Ar value 452.It Fl x 453Same as 454.Fl o Cm retrans Ns = Ns Aq Ar value 455.El 456.Sh SEE ALSO 457.Xr nmount 2 , 458.Xr unmount 2 , 459.Xr nfsv4 4 , 460.Xr fstab 5 , 461.Xr gssd 8 , 462.Xr mount 8 , 463.Xr nfsd 8 , 464.Xr nfsiod 8 , 465.Xr showmount 8 466.Sh BUGS 467Since nfsv4 performs open/lock operations that have their ordering strictly 468enforced by the server, the options 469.Cm intr 470and 471.Cm soft 472cannot be safely used. 473.Cm hard 474nfsv4 mounts are strongly recommended. 475