Print this page
5956 orientate is not a word
Reviewed by: Garrett D'Amore <garrett@damore.org>
Reviewed by: Marcel Telka <marcel@telka.sk>
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1m/mount_nfs.1m
+++ new/usr/src/man/man1m/mount_nfs.1m
1 1 '\" te
2 2 .\" Copyright (c) 2009 Sun Microsystems, Inc. All Rights Reserved
3 3 .\" Copyright 1989 AT&T
4 4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
5 5 .\" See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the
6 6 .\" fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 -.TH MOUNT_NFS 1M "Jul 26, 2009"
7 +.TH MOUNT_NFS 1M "Jun 3, 2015"
8 8 .SH NAME
9 9 mount_nfs \- mount remote NFS resources
10 10 .SH SYNOPSIS
11 11 .LP
12 12 .nf
13 13 \fBmount\fR [\fB-F\fR nfs] [\fIgeneric_options\fR] [\fB-o\fR \fIspecific_options\fR] [\fB-O\fR] \fIresource\fR
14 14 .fi
15 15
16 16 .LP
17 17 .nf
18 18 \fBmount\fR [\fB-F\fR nfs] [\fIgeneric_options\fR] [\fB-o\fR \fIspecific_options\fR] [\fB-O\fR] \fImount_point\fR
19 19 .fi
20 20
21 21 .LP
22 22 .nf
23 23 \fBmount\fR [\fB-F\fR nfs] [\fIgeneric_options\fR] [\fB-o\fR \fIspecific_options\fR]
24 24 [\fB-O\fR] \fIresource\fR \fImount_point\fR
25 25 .fi
26 26
27 27 .SH DESCRIPTION
28 28 .sp
29 29 .LP
30 30 The \fBmount\fR utility attaches a named \fIresource\fR to the file system
31 31 hierarchy at the pathname location \fImount_point\fR, which must already exist.
32 32 If \fImount_point\fR has any contents prior to the \fBmount\fR operation, the
33 33 contents remain hidden until the \fIresource\fR is once again unmounted.
34 34 .sp
35 35 .LP
36 36 \fBmount_nfs\fR starts the \fBlockd\fR(1M) and \fBstatd\fR(1M) daemons if they
37 37 are not already running.
38 38 .sp
39 39 .LP
40 40 If the resource is listed in the \fB/etc/vfstab\fR file, the command line can
41 41 specify either \fIresource\fR or \fImount_point\fR, and \fBmount\fR consults
42 42 \fB/etc/vfstab\fR for more information. If the \fB-F\fR option is omitted,
43 43 \fBmount\fR takes the file system type from \fB/etc/vfstab\fR.
44 44 .sp
45 45 .LP
46 46 If the resource is not listed in the \fB/etc/vfstab\fR file, then the command
47 47 line must specify both the \fIresource\fR and the \fImount_point\fR.
48 48 .sp
49 49 .LP
50 50 \fIhost\fR can be an IPv4 or IPv6 address string. As IPv6 addresses already
51 51 contain colons, enclose \fIhost\fR in a pair of square brackets when specifying
52 52 an IPv6 address string. Otherwise the first occurrence of a colon can be
53 53 interpreted as the separator between the host name and path, for example,
54 54 \fB[1080::8:800:200C:417A]:tmp/file\fR. See \fBinet\fR(7P) and \fBinet6\fR(7P).
55 55 .sp
56 56 .ne 2
57 57 .na
58 58 \fB\fIhost\fR:\fIpathname\fR\fR
59 59 .ad
60 60 .sp .6
61 61 .RS 4n
62 62 Where \fIhost\fR is the name of the \fBNFS\fR server host, and \fIpathname\fR
63 63 is the path name of the directory on the server being mounted. The path name is
64 64 interpreted according to the server's path name parsing rules and is not
65 65 necessarily slash-separated, though on most servers, this is the case.
66 66 .RE
67 67
68 68 .sp
69 69 .ne 2
70 70 .na
71 71 \fB\fInfs\fR://\fIhost\fR[:\fIport\fR]/\fIpathname\fR\fR
72 72 .ad
73 73 .sp .6
74 74 .RS 4n
75 75 This is an \fBNFS\fR \fBURL\fR and follows the standard convention for
76 76 \fBNFS\fR \fBURL\fRs as described in \fINFS URL Scheme\fR, RFC 2224. See the
77 77 discussion of \fBURL\fR's and the public option under \fBNFS FILE SYSTEMS\fR
78 78 for a more detailed discussion.
79 79 .RE
80 80
81 81 .sp
82 82 .ne 2
83 83 .na
84 84 \fB\fIhost\fR:\fIpathname\fR
85 85 \fInfs\fR://\fIhost\fR[:\fIport\fR]/\fIpathname\fR\fR
86 86 .ad
87 87 .br
88 88 .na
89 89 \fB\fR
90 90 .ad
91 91 .sp .6
92 92 .RS 4n
93 93 \fIhost\fR:\fIpathname\fR is a comma-separated list of
94 94 \fIhost\fR:\fIpathname\fR.
95 95 .sp
96 96 See the discussion of replicated file systems and failover under \fBNFS FILE
97 97 SYSTEMS\fR for a more detailed discussion.
98 98 .RE
99 99
100 100 .sp
101 101 .ne 2
102 102 .na
103 103 \fB\fIhostlist\fR \fIpathname\fR\fR
104 104 .ad
105 105 .sp .6
106 106 .RS 4n
107 107 \fIhostlist\fR is a comma-separated list of hosts.
108 108 .sp
109 109 See the discussion of replicated file systems and failover under \fBNFS FILE
110 110 SYSTEMS\fR for a more detailed discussion.
111 111 .RE
112 112
113 113 .sp
114 114 .LP
115 115 The \fBmount\fR command maintains a table of mounted file systems in
116 116 \fB/etc/mnttab\fR, described in \fBmnttab\fR(4).
117 117 .sp
118 118 .LP
119 119 \fBmount_nfs\fR supports both NFSv3 and NFSv4 mounts. The default NFS version
120 120 is NFSv4.
121 121 .SH OPTIONS
122 122 .sp
123 123 .LP
124 124 See \fBmount\fR(1M) for the list of supported \fIgeneric_options\fR. See
125 125 \fBshare_nfs\fR(1M) for a description of server options.
126 126 .sp
127 127 .ne 2
128 128 .na
129 129 \fB\fB-o\fR \fIspecific_options\fR\fR
130 130 .ad
131 131 .sp .6
132 132 .RS 4n
133 133 Set file system specific options according to a comma-separated list with no
134 134 intervening spaces.
135 135 .sp
136 136 .ne 2
137 137 .na
138 138 \fB\fBacdirmax=\fR\fIn\fR\fR
139 139 .ad
140 140 .sp .6
141 141 .RS 4n
142 142 Hold cached attributes for no more than \fIn\fR seconds after directory update.
143 143 The default value is \fB60\fR.
144 144 .RE
145 145
146 146 .sp
147 147 .ne 2
148 148 .na
149 149 \fB\fBacdirmin=\fR\fIn\fR\fR
150 150 .ad
151 151 .sp .6
152 152 .RS 4n
153 153 Hold cached attributes for at least \fIn\fR seconds after directory update. The
154 154 default value is \fB30\fR.
155 155 .RE
156 156
157 157 .sp
158 158 .ne 2
159 159 .na
160 160 \fB\fBacregmax=\fR\fIn\fR\fR
161 161 .ad
162 162 .sp .6
163 163 .RS 4n
164 164 Hold cached attributes for no more than \fIn\fR seconds after file
165 165 modification. The default value is \fB60\fR.
166 166 .RE
167 167
168 168 .sp
169 169 .ne 2
170 170 .na
171 171 \fB\fBacregmin=\fR\fIn\fR\fR
172 172 .ad
173 173 .sp .6
174 174 .RS 4n
175 175 Hold cached attributes for at least \fIn\fR seconds after file modification.
176 176 The default value is \fB3\fR.
177 177 .RE
178 178
179 179 .sp
180 180 .ne 2
181 181 .na
182 182 \fB\fBactimeo=\fR\fIn\fR\fR
183 183 .ad
184 184 .sp .6
185 185 .RS 4n
186 186 Set \fImin\fR and \fImax\fR times for regular files and directories to \fIn\fR
187 187 seconds. See "File Attributes," below, for a description of the effect of
188 188 setting this option to \fB0\fR.
189 189 .sp
190 190 See "Specifying Values for Attribute Cache Duration Options," below, for a
191 191 description of how \fBacdirmax\fR, \fBacdirmin\fR, \fBacregmax\fR,
192 192 \fBacregmin\fR, and \fBactimeo\fR are parsed on a \fBmount\fR command line.
193 193 .RE
194 194
195 195 .sp
196 196 .ne 2
197 197 .na
198 198 \fB\fBbg\fR | \fBfg\fR\fR
199 199 .ad
200 200 .sp .6
201 201 .RS 4n
202 202 If the first attempt fails, retry in the background, or, in the foreground. The
203 203 default is \fBfg\fR.
204 204 .RE
205 205
206 206 .sp
207 207 .ne 2
208 208 .na
209 209 \fB\fBforcedirectio\fR | \fBnoforcedirectio\fR\fR
210 210 .ad
211 211 .sp .6
212 212 .RS 4n
213 213 If \fBforcedirectio\fR is specified, then for the duration of the mount, forced
214 214 direct \fBI/O\fR is used. If the filesystem is mounted using
215 215 \fBforcedirectio\fR, data is transferred directly between client and server,
216 216 with no buffering on the client. If the filesystem is mounted using
217 217 \fBnoforcedirectio\fR, data is buffered on the client. \fBforcedirectio\fR is a
218 218 performance option that is of benefit only in large sequential data transfers.
219 219 The default behavior is \fBnoforcedirectio\fR.
220 220 .RE
221 221
222 222 .sp
223 223 .ne 2
224 224 .na
225 225 \fB\fBgrpid\fR\fR
226 226 .ad
227 227 .sp .6
228 228 .RS 4n
229 229 By default, the \fBGID\fR associated with a newly created file obeys the System
230 230 V semantics; that is, the \fBGID\fR is set to the effective \fBGID\fR of the
231 231 calling process. This behavior can be overridden on a per-directory basis by
232 232 setting the set-GID bit of the parent directory; in this case, the \fBGID\fR of
233 233 a newly created file is set to the \fBGID\fR of the parent directory (see
234 234 \fBopen\fR(2) and \fBmkdir\fR(2)). Files created on file systems that are
235 235 mounted with the \fBgrpid\fR option obeys \fBBSD\fR semantics independent of
236 236 whether the set-GID bit of the parent directory is set; that is, the \fBGID\fR
237 237 is unconditionally inherited from that of the parent directory.
238 238 .RE
239 239
240 240 .sp
241 241 .ne 2
242 242 .na
243 243 \fB\fBhard\fR | \fBsoft\fR\fR
244 244 .ad
245 245 .sp .6
246 246 .RS 4n
247 247 Continue to retry requests until the server responds (\fBhard\fR) or give up
248 248 and return an error (\fBsoft\fR). The default value is \fBhard\fR. Note that
249 249 NFSv4 clients do not support soft mounts.
250 250 .RE
251 251
252 252 .sp
253 253 .ne 2
254 254 .na
255 255 \fB\fBintr\fR | \fBnointr\fR\fR
256 256 .ad
257 257 .sp .6
258 258 .RS 4n
259 259 Allow (do not allow) keyboard interrupts to kill a process that is hung while
260 260 waiting for a response on a hard-mounted file system. The default is
261 261 \fBintr\fR, which makes it possible for clients to interrupt applications that
262 262 can be waiting for a remote mount.
263 263 .RE
264 264
265 265 .sp
266 266 .ne 2
267 267 .na
268 268 \fB\fBnoac\fR\fR
269 269 .ad
270 270 .sp .6
271 271 .RS 4n
272 272 Suppress data and attribute caching. The data caching that is suppressed is the
273 273 write-behind. The local page cache is still maintained, but data copied into it
274 274 is immediately written to the server.
275 275 .RE
276 276
277 277 .sp
278 278 .ne 2
279 279 .na
280 280 \fB\fBnocto\fR\fR
281 281 .ad
282 282 .sp .6
283 283 .RS 4n
284 284 Do not perform the normal close-to-open consistency. When a file is closed, all
285 285 modified data associated with the file is flushed to the server and not held on
286 286 the client. When a file is opened the client sends a request to the server to
287 287 validate the client's local caches. This behavior ensures a file's consistency
288 288 across multiple NFS clients. When \fB-nocto\fR is in effect, the client does
289 289 not perform the flush on close and the request for validation, allowing the
290 290 possiblity of differences among copies of the same file as stored on multiple
291 291 clients.
292 292 .sp
293 293 This option can be used where it can be guaranteed that accesses to a specified
294 294 file system are made from only one client and only that client. Under such a
295 295 condition, the effect of \fB-nocto\fR can be a slight performance gain.
296 296 .RE
297 297
298 298 .sp
299 299 .ne 2
300 300 .na
301 301 \fB\fBport=\fR\fIn\fR\fR
302 302 .ad
303 303 .sp .6
304 304 .RS 4n
305 305 The server \fBIP\fR port number. The default is \fBNFS_PORT\fR. If the
306 306 \fBport\fR option is specified, and if the resource includes one or more
307 307 \fBNFS\fR \fBURL\fRs, and if any of the \fBURL\fRs include a \fBport\fR number,
308 308 then the \fBport\fR number in the option and in the \fBURL\fR must be the same.
309 309 .RE
310 310
311 311 .sp
312 312 .ne 2
313 313 .na
314 314 \fB\fBposix\fR\fR
315 315 .ad
316 316 .sp .6
317 317 .RS 4n
318 318 Request \fBPOSIX.1\fR semantics for the file system. Requires a mount Version 2
319 319 \fBmountd\fR(1M) on the server. See \fBstandards\fR(5) for information
320 320 regarding POSIX.
321 321 .RE
322 322
323 323 .sp
324 324 .ne 2
325 325 .na
326 326 \fB\fBproto=\fR\fInetid\fR | \fBrdma\fR\fR
327 327 .ad
328 328 .sp .6
329 329 .RS 4n
330 330 By default, the transport protocol that the NFS mount uses is the first
331 331 available RDMA transport supported both by the client and the server. If no
332 332 RDMA transport is found, then it attempts to use a TCP transport or, failing
333 333 that, a UDP transport, as ordered in the \fB/etc/netconfig\fR file. If it does
334 334 not find a connection oriented transport, it uses the first available
335 335 connectionless transport.
336 336 .sp
337 337 Use this option to override the default behavior.
338 338 .sp
339 339 \fBproto\fR is set to the value of \fInetid\fR or \fBrdma\fR. \fInetid\fR is
340 340 the value of the \fBnetwork_id\fR field entry in the \fB/etc/netconfig\fR file.
341 341 .sp
342 342 The UDP protocol is not supported for NFS Version 4. If you specify a UDP
343 343 protocol with the \fBproto\fR option, NFS version 4 is not used.
344 344 .RE
345 345
346 346 .sp
347 347 .ne 2
348 348 .na
349 349 \fB\fBpublic\fR\fR
350 350 .ad
351 351 .sp .6
352 352 .RS 4n
353 353 The \fBpublic\fR option forces the use of the public file handle when
354 354 connecting to the \fBNFS\fR server. The resource specified might not have an
355 355 \fBNFS\fR \fBURL\fR. See the discussion of \fBURL\fRs and the public option
356 356 under \fBNFS FILE SYSTEMS\fR for a more detailed discussion.
357 357 .RE
358 358
359 359 .sp
360 360 .ne 2
361 361 .na
362 362 \fB\fBquota\fR | \fBnoquota\fR\fR
363 363 .ad
364 364 .sp .6
365 365 .RS 4n
366 366 Enable or prevent \fBquota\fR(1M) to check whether the user is over quota on
367 367 this file system; if the file system has quotas enabled on the server, quotas
368 368 are still checked for operations on this file system.
369 369 .RE
370 370
371 371 .sp
372 372 .ne 2
373 373 .na
374 374 \fB\fBremount\fR\fR
375 375 .ad
376 376 .sp .6
377 377 .RS 4n
378 378 Remounts a read-only file system as read-write (using the \fBrw\fR option).
379 379 This option cannot be used with other \fB-o\fR options, and this option works
380 380 only on currently mounted read-only file systems.
381 381 .RE
382 382
383 383 .sp
384 384 .ne 2
385 385 .na
386 386 \fB\fBretrans=\fR\fIn\fR\fR
387 387 .ad
388 388 .sp .6
389 389 .RS 4n
390 390 Set the number of \fBNFS\fR retransmissions to \fIn\fR. The default value is
391 391 \fB5\fR. For connection-oriented transports, this option has no effect because
392 392 it is assumed that the transport performs retransmissions on behalf of NFS.
393 393 .RE
394 394
395 395 .sp
396 396 .ne 2
397 397 .na
398 398 \fB\fBretry=\fR\fIn\fR\fR
399 399 .ad
400 400 .sp .6
401 401 .RS 4n
402 402 The number of times to retry the \fBmount\fR operation. The default for the
403 403 \fBmount\fR command is \fB10000\fR.
404 404 .sp
405 405 The default for the automounter is \fB0\fR, in other words, do not retry. You
406 406 might find it useful to increase this value on heavily loaded servers, where
407 407 automounter traffic is dropped, causing unnecessary server not responding
408 408 errors.
|
↓ open down ↓ |
391 lines elided |
↑ open up ↑ |
409 409 .RE
410 410
411 411 .sp
412 412 .ne 2
413 413 .na
414 414 \fB\fBrsize=\fR\fIn\fR\fR
415 415 .ad
416 416 .sp .6
417 417 .RS 4n
418 418 Set the read buffer size to a maximum of \fIn\fR bytes. The default value is
419 -\fB1048576\fR when using connection-orientated transports with Version 3 or
419 +\fB1048576\fR when using connection-oriented transports with Version 3 or
420 420 Version 4 of the \fBNFS\fR protocol, and \fB32768\fR when using connection-less
421 421 transports. The default can be negotiated down if the server prefers a smaller
422 422 transfer size. "\fBRead\fR" operations may not necessarily use the maximum
423 423 buffer size. When using Version 2, the default value is \fB32768\fR for all
424 424 transports.
425 425 .RE
426 426
427 427 .sp
428 428 .ne 2
429 429 .na
430 430 \fB\fBsec=\fR\fImode\fR\fR
431 431 .ad
432 432 .sp .6
433 433 .RS 4n
434 434 Set the security \fImode\fR for \fBNFS\fR transactions. If \fBsec=\fR is not
435 435 specified, then the default action is to use \fBAUTH_SYS\fR over \fBNFS\fR
436 436 Version 2 mounts, use a user-configured default \fBauth\fR over NFS version 3
437 437 mounts, or to negotiate a mode over Version 4 mounts.
438 438 .sp
439 439 The preferred mode for NFS Version 3 mounts is the default mode specified in
440 440 \fB/etc/nfssec.conf\fR (see \fBnfssec.conf\fR(4)) on the client. If there is no
441 441 default configured in this file or if the server does not export using the
442 442 client's default mode, then the client picks the first mode that it supports in
443 443 the array of modes returned by the server. These alternatives are limited to
444 444 the security flavors listed in \fB/etc/nfssec.conf\fR.
445 445 .sp
446 446 NFS Version 4 mounts negotiate a security mode when the server returns an array
447 447 of security modes. The client attempts the mount with each security mode, in
448 448 order, until one is successful.
449 449 .sp
450 450 Only one mode can be specified with the \fBsec=\fR option. See \fBnfssec\fR(5)
451 451 for the available \fImode\fR options.
452 452 .RE
453 453
454 454 .sp
455 455 .ne 2
456 456 .na
457 457 \fB\fBsecure\fR\fR
458 458 .ad
459 459 .sp .6
460 460 .RS 4n
461 461 This option has been deprecated in favor of the \fBsec=\fR\fIdh\fR option.
462 462 .RE
463 463
464 464 .sp
465 465 .ne 2
466 466 .na
467 467 \fB\fBtimeo=\fR\fIn\fR\fR
468 468 .ad
469 469 .sp .6
470 470 .RS 4n
471 471 Set the \fBNFS\fR timeout to \fIn\fR tenths of a second. The default value is
472 472 \fB11\fR tenths of a second for connectionless transports, and \fB600\fR tenths
473 473 of a second for connection-oriented transports. This value is ignored for
474 474 connectionless transports. Such transports might implement their own timeouts,
475 475 which are outside the control of NFS.
476 476 .RE
477 477
478 478 .sp
479 479 .ne 2
480 480 .na
481 481 \fB\fBvers=\fR\fINFS version number\fR\fR
482 482 .ad
483 483 .sp .6
484 484 .RS 4n
485 485 By default, the version of \fBNFS\fR protocol used between the client and the
486 486 server is the highest one available on both systems. The default maximum for
487 487 the client is Version 4. This can be changed by setting the
488 488 \fBNFS_CLIENT_VERSMAX\fR parameter in \fB/etc/default/nfs\fR to a valid version
489 489 (2, 3, or 4). If the \fBNFS\fR server does not support the client's default
490 490 maximum, the next lowest version attempted until a matching version is found.
|
↓ open down ↓ |
61 lines elided |
↑ open up ↑ |
491 491 .RE
492 492
493 493 .sp
494 494 .ne 2
495 495 .na
496 496 \fB\fBwsize=\fR\fIn\fR\fR
497 497 .ad
498 498 .sp .6
499 499 .RS 4n
500 500 Set the write buffer size to a maximum of \fIn\fR bytes. The default value is
501 -\fB1048576\fR when using connection-orientated transports with Version 3 or
501 +\fB1048576\fR when using connection-oriented transports with Version 3 or
502 502 Version 4 of the \fBNFS\fR protocol, and \fB32768\fR when using connection-less
503 503 transports. The default can be negotiated down if the server prefers a smaller
504 504 transfer size. "\fBWrite\fR" operations may not necessarily use the maximum
505 505 buffer size. When using Version 2, the default value is \fB32768\fR for all
506 506 transports.
507 507 .RE
508 508
509 509 .sp
510 510 .ne 2
511 511 .na
512 512 \fB\fBxattr\fR | \fBnoxattr\fR\fR
513 513 .ad
514 514 .sp .6
515 515 .RS 4n
516 516 Allow or disallow the creation and manipulation of extended attributes. The
517 517 default is \fBxattr\fR. See \fBfsattr\fR(5) for a description of extended
518 518 attributes.
519 519 .RE
520 520
521 521 .RE
522 522
523 523 .sp
524 524 .ne 2
525 525 .na
526 526 \fB\fB-O\fR\fR
527 527 .ad
528 528 .sp .6
529 529 .RS 4n
530 530 Overlay mount. Allow the file system to be mounted over an existing mount
531 531 point, making the underlying file system inaccessible. If a mount is attempted
532 532 on a pre-existing mount point without setting this flag, the mount fails,
533 533 producing the error "device busy."
534 534 .RE
535 535
536 536 .SH NFS FILE SYSTEMS
537 537 .sp
538 538 .ne 2
539 539 .na
540 540 \fBBackground versus Foreground\fR
541 541 .ad
542 542 .sp .6
543 543 .RS 4n
544 544 File systems mounted with the \fBbg\fR option indicate that \fBmount\fR is to
545 545 retry in the background if the server's mount daemon (\fBmountd\fR(1M)) does
546 546 not respond. \fBmount\fR retries the request up to the count specified in the
547 547 \fBretry=\fR\fIn\fR option. (Note that the default value for \fBretry\fR
548 548 differs between \fBmount\fR and \fBautomount\fR. See the description of
549 549 \fBretry\fR, above.) Once the file system is mounted, each \fBNFS\fR request
550 550 made in the kernel waits \fBtimeo=\fR\fIn\fR tenths of a second for a response.
551 551 If no response arrives, the time-out is multiplied by \fB2\fR and the request
552 552 is retransmitted. When the number of retransmissions has reached the number
553 553 specified in the \fBretrans=\fR\fIn\fR option, a file system mounted with the
554 554 \fBsoft\fR option returns an error on the request; one mounted with the
555 555 \fBhard\fR option prints a warning message and continues to retry the request.
556 556 .RE
557 557
558 558 .sp
559 559 .ne 2
560 560 .na
561 561 \fBHard versus Soft\fR
562 562 .ad
563 563 .sp .6
564 564 .RS 4n
565 565 File systems that are mounted read-write or that contain executable files
566 566 should always be mounted with the \fBhard\fR option. Applications using
567 567 \fBsoft\fR mounted file systems can incur unexpected \fBI/O\fR errors, file
568 568 corruption, and unexpected program core dumps. The soft option is not
569 569 recommended.
570 570 .RE
571 571
572 572 .sp
573 573 .ne 2
574 574 .na
575 575 \fBAuthenticated requests\fR
576 576 .ad
577 577 .sp .6
578 578 .RS 4n
579 579 The server can require authenticated \fBNFS\fR requests from the client.
580 580 \fBsec=\fR\fIdh\fR authentication might be required. See \fBnfssec\fR(5).
581 581 .RE
582 582
583 583 .sp
584 584 .ne 2
585 585 .na
586 586 \fBURLs and the public option\fR
587 587 .ad
588 588 .sp .6
589 589 .RS 4n
590 590 If the \fBpublic\fR option is specified, or if the \fIresource\fR includes and
591 591 \fBNFS\fR \fBURL\fR, \fBmount\fR attempts to connect to the server using the
592 592 public file handle lookup protocol. See \fIWebNFS Client Specification\fR, RFC
593 593 2054. If the server supports the public file handle, the attempt is successful;
594 594 \fBmount\fR does not need to contact the server's \fBrpcbind\fR(1M) and the
595 595 \fBmountd\fR(1M) daemons to get the port number of the \fBmount\fR server and
596 596 the initial file handle of \fIpathname\fR, respectively. If the \fBNFS\fR
597 597 client and server are separated by a firewall that allows all outbound
598 598 connections through specific ports, such as \fBNFS_PORT\fR, then this enables
599 599 \fBNFS\fR operations through the firewall. The public option and the \fBNFS\fR
600 600 \fBURL\fR can be specified independently or together. They interact as
601 601 specified in the following matrix:
602 602 .sp
603 603 .in +2
604 604 .nf
605 605 Resource Style
606 606
607 607 \fIhost\fR:\fIpathname\fR NFS URL
608 608
609 609 public option Force public file Force public file
610 610 handle and fail handle and fail
611 611 mount if not supported. mount if not supported.
612 612
613 613 Use Native paths. Use Canonical paths.
614 614
615 615 default Use MOUNT protocol. Try public file handle
616 616 with Canonical paths.
617 617 Fall back to MOUNT
618 618 protocol if not
619 619 supported.
620 620 .fi
621 621 .in -2
622 622
623 623 A Native path is a path name that is interpreted according to conventions used
624 624 on the native operating system of the \fBNFS\fR server. A Canonical path is a
625 625 path name that is interpreted according to the \fBURL\fR rules. See \fIUniform
626 626 Resource Locators (URL)\fR, RFC 1738. See for uses of Native and Canonical
627 627 paths.
628 628 .RE
629 629
630 630 .sp
631 631 .ne 2
632 632 .na
633 633 \fBReplicated file systems and failover\fR
634 634 .ad
635 635 .sp .6
636 636 .RS 4n
637 637 \fIresource\fR can list multiple read\(mionly file systems to be used to
638 638 provide data. These file systems should contain equivalent directory structures
639 639 and identical files. It is also recommended that they be created by a utility
640 640 such as \fBrdist\fR(1). The file systems can be specified either with a
641 641 comma\(miseparated list of \fIhost:/pathname\fR entries and/or \fBNFS\fR
642 642 \fBURL\fR entries, or with a comma \(miseparated list of hosts, if all file
643 643 system names are the same. If multiple file systems are named and the first
644 644 server in the list is down, failover uses the next alternate server to access
645 645 files. If the read\(mionly option is not chosen, replication is disabled. File
646 646 access, for NFS Versions 2 and 3, is blocked on the original if NFS locks are
647 647 active for that file.
648 648 .RE
649 649
650 650 .SS "File Attributes"
651 651 .sp
652 652 .LP
653 653 To improve \fBNFS\fR read performance, files and file attributes are cached.
654 654 File modification times get updated whenever a write occurs. However, file
655 655 access times can be temporarily out-of-date until the cache gets refreshed.
656 656 .sp
657 657 .LP
658 658 The attribute cache retains file attributes on the client. Attributes for a
659 659 file are assigned a time to be flushed. If the file is modified before the
660 660 flush time, then the flush time is extended by the time since the last
661 661 modification (under the assumption that files that changed recently are likely
662 662 to change soon). There is a minimum and maximum flush time extension for
663 663 regular files and for directories. Setting \fBactimeo=\fR\fIn\fR sets flush
664 664 time to \fIn\fR seconds for both regular files and directories.
665 665 .sp
666 666 .LP
667 667 Setting \fBactimeo=0\fR disables attribute caching on the client. This means
668 668 that every reference to attributes is satisfied directly from the server though
669 669 file data is still cached. While this guarantees that the client always has the
670 670 latest file attributes from the server, it has an adverse effect on performance
671 671 through additional latency, network load, and server load.
672 672 .sp
673 673 .LP
674 674 Setting the \fBnoac\fR option also disables attribute caching, but has the
675 675 further effect of disabling client write caching. While this guarantees that
676 676 data written by an application is written directly to a server, where it can be
677 677 viewed immediately by other clients, it has a significant adverse effect on
678 678 client write performance. Data written into memory-mapped file pages
679 679 (\fBmmap\fR(2)) are not written directly to this server.
680 680 .SS "Specifying Values for Attribute Cache Duration Options"
681 681 .sp
682 682 .LP
683 683 The attribute cache duration options are \fBacdirmax\fR, \fBacdirmin\fR,
684 684 \fBacregmax\fR, \fBacregmin\fR, and \fBactimeo\fR, as described under OPTIONS.
685 685 A value specified for \fBactimeo\fR sets the values of all attribute cache
686 686 duration options except for any of these options specified following
687 687 \fBactimeo\fR on a \fBmount\fR command line. For example, consider the
688 688 following command:
689 689 .sp
690 690 .in +2
691 691 .nf
692 692 example# mount -o acdirmax=10,actimeo=1000 server:/path /localpath
693 693 .fi
694 694 .in -2
695 695
696 696 .sp
697 697 .LP
698 698 Because \fBactimeo\fR is the last duration option in the command line, its
699 699 value (\fB1000\fR) becomes the setting for all of the duration options,
700 700 including \fBacdirmax\fR. Now consider:
701 701 .sp
702 702 .in +2
703 703 .nf
704 704 example# mount -o actimeo=1000,acdirmax=10 server:/path /localpath
705 705 .fi
706 706 .in -2
707 707
708 708 .sp
709 709 .LP
710 710 Because the \fBacdirmax\fR option follows \fBactimeo\fR on the command line, it
711 711 is assigned the value specified (\fB10\fR). The remaining duration options are
712 712 set to the value of \fBactimeo\fR (\fB1000\fR).
713 713 .SH EXAMPLES
714 714 .LP
715 715 \fBExample 1 \fRMounting an \fBNFS\fR File System
716 716 .sp
717 717 .LP
718 718 To mount an \fBNFS\fR file system:
719 719
720 720 .sp
721 721 .in +2
722 722 .nf
723 723 example# mount serv:/usr/src /usr/src
724 724 .fi
725 725 .in -2
726 726 .sp
727 727
728 728 .LP
729 729 \fBExample 2 \fRMounting An \fBNFS\fR File System Read-Only With No suid
730 730 Privileges
731 731 .sp
732 732 .LP
733 733 To mount an \fBNFS\fR file system read-only with no suid privileges:
734 734
735 735 .sp
736 736 .in +2
737 737 .nf
738 738 example# mount -r -o nosuid serv:/usr/src /usr/src
739 739 .fi
740 740 .in -2
741 741 .sp
742 742
743 743 .LP
744 744 \fBExample 3 \fRMounting An \fBNFS\fR File System Over Version 2, with the UDP
745 745 Transport
746 746 .sp
747 747 .LP
748 748 To mount an \fBNFS\fR file system over Version 2, with the UDP transport:
749 749
750 750 .sp
751 751 .in +2
752 752 .nf
753 753 example# mount -o vers=2,proto=udp serv:/usr/src /usr/src
754 754 .fi
755 755 .in -2
756 756 .sp
757 757
758 758 .LP
759 759 \fBExample 4 \fRMounting an \fBNFS\fR File System Using An \fBNFS\fR \fBURL\fR
760 760 .sp
761 761 .LP
762 762 To mount an \fBNFS\fR file system using an \fBNFS\fR \fBURL\fR (a canonical
763 763 path):
764 764
765 765 .sp
766 766 .in +2
767 767 .nf
768 768 example# mount nfs://serv/usr/man /usr/man
769 769 .fi
770 770 .in -2
771 771 .sp
772 772
773 773 .LP
774 774 \fBExample 5 \fRMounting An \fBNFS\fR File System Forcing Use Of The Public
775 775 File Handle
776 776 .sp
777 777 .LP
778 778 To mount an \fBNFS\fR file system and force the use of the public file handle
779 779 and an \fBNFS\fR \fBURL\fR (a canonical path) that has a non 7-bit ASCII escape
780 780 sequence:
781 781
782 782 .sp
783 783 .in +2
784 784 .nf
785 785 example# mount -o public nfs://serv/usr/%A0abc /mnt/test
786 786 .fi
787 787 .in -2
788 788 .sp
789 789
790 790 .LP
791 791 \fBExample 6 \fRMounting an \fBNFS\fR File System Using a Native Path
792 792 .sp
793 793 .LP
794 794 To mount an \fBNFS\fR file system using a native path (where the server uses
795 795 colons (":") as the component separator) and the public file handle:
796 796
797 797 .sp
798 798 .in +2
799 799 .nf
800 800 example# mount -o public serv:C:doc:new /usr/doc
801 801 .fi
802 802 .in -2
803 803 .sp
804 804
805 805 .LP
806 806 \fBExample 7 \fRMounting a Replicated Set of \fBNFS\fR File Systems with the
807 807 Same Pathnames
808 808 .sp
809 809 .LP
810 810 To mount a replicated set of \fBNFS\fR file systems with the same pathnames:
811 811
812 812 .sp
813 813 .in +2
814 814 .nf
815 815 example# mount serv\(mia,serv\(mib,serv\(mic:/usr/man /usr/man
816 816 .fi
817 817 .in -2
818 818 .sp
819 819
820 820 .LP
821 821 \fBExample 8 \fRMounting a Replicated Set of \fBNFS\fR File Systems with
822 822 Different Pathnames
823 823 .sp
824 824 .LP
825 825 To mount a replicated set of \fBNFS\fR file systems with different pathnames:
826 826
827 827 .sp
828 828 .in +2
829 829 .nf
830 830 example# mount serv\(mix:/usr/man,serv\(miy:/var/man,nfs://serv-z/man /usr/man
831 831 .fi
832 832 .in -2
833 833 .sp
834 834
835 835 .SH FILES
836 836 .sp
837 837 .ne 2
838 838 .na
839 839 \fB\fB/etc/mnttab\fR\fR
840 840 .ad
841 841 .sp .6
842 842 .RS 4n
843 843 table of mounted file systems
844 844 .RE
845 845
846 846 .sp
847 847 .ne 2
848 848 .na
849 849 \fB\fB/etc/dfs/fstypes\fR\fR
850 850 .ad
851 851 .sp .6
852 852 .RS 4n
853 853 default distributed file system type
854 854 .RE
855 855
856 856 .sp
857 857 .ne 2
858 858 .na
859 859 \fB\fB/etc/vfstab\fR\fR
860 860 .ad
861 861 .sp .6
862 862 .RS 4n
863 863 table of automatically mounted resources
864 864 .RE
865 865
866 866 .SH SEE ALSO
867 867 .sp
868 868 .LP
869 869 \fBrdist\fR(1), \fBlockd\fR(1M), \fBmountall\fR(1M), \fBmountd\fR(1M),
870 870 \fBnfsd\fR(1M), \fBquota\fR(1M), \fBstatd\fR(1M), \fBmkdir\fR(2),
871 871 \fBmmap\fR(2), \fBmount\fR(2), \fBopen\fR(2), \fBumount\fR(2), \fBmnttab\fR(4),
872 872 \fBnfs\fR(4), \fBnfssec.conf\fR(4), \fBattributes\fR(5), \fBfsattr\fR(5),
873 873 \fBnfssec\fR(5), \fBstandards\fR(5), \fBinet\fR(7P), \fBinet6\fR(7P),
874 874 \fBlofs\fR(7FS)
875 875 .sp
876 876 .LP
877 877 Callaghan, Brent, \fIWebNFS Client Specification\fR, RFC 2054, October 1996.
878 878 .sp
879 879 .LP
880 880 Callaghan, Brent, \fINFS URL Scheme\fR, RFC 2224, October 1997.
881 881 .sp
882 882 .LP
883 883 Berners-Lee, Masinter & McCahill , \fIUniform Resource Locators (URL)\fR, RFC
884 884 1738, December 1994.
885 885 .SH NOTES
886 886 .sp
887 887 .LP
888 888 An \fBNFS\fR server should not attempt to mount its own file systems. See
889 889 \fBlofs\fR(7FS).
890 890 .sp
891 891 .LP
892 892 If the directory on which a file system is to be mounted is a symbolic link,
893 893 the file system is mounted on \fBthe directory to which the symbolic link
894 894 refers,\fR rather than being mounted on top of the symbolic link itself.
895 895 .sp
896 896 .LP
897 897 SunOS 4.x used the \fBbiod\fR maintenance procedure to perform parallel
898 898 read-ahead and write-behind on \fBNFS\fR clients. SunOS 5.x made \fBbiod\fR
899 899 obsolete with multi-threaded processing, which transparently performs parallel
900 900 read-ahead and write-behind.
901 901 .sp
902 902 .LP
903 903 Since the root \fB(\fR/\fB)\fR file system is mounted read-only by the kernel
904 904 during the boot process, only the \fBremount\fR option (and options that can be
905 905 used in conjunction with \fBremount\fR) affect the root (\fB/\fR) entry in the
906 906 \fB/etc/vfstab\fR file.
907 907 .sp
908 908 .LP
909 909 \fBmount_cachefs\fR cannot be used with replicated NFS mounts or any NFS
910 910 Version 4 mount.
911 911 .sp
912 912 .LP
913 913 The NFS client service is managed by the service management facility,
914 914 \fBsmf\fR(5), under the service identifier:
915 915 .sp
916 916 .in +2
917 917 .nf
918 918 svc:/network/nfs/client:default
919 919 .fi
920 920 .in -2
921 921 .sp
922 922
923 923 .sp
924 924 .LP
925 925 Administrative actions on this service, such as enabling, disabling, or
926 926 requesting restart, can be performed using \fBsvcadm\fR(1M). The service's
927 927 status can be queried using the \fBsvcs\fR(1) command.
|
↓ open down ↓ |
416 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX