Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ./../../../../.././../usr/man/man8/mount_nfs.8
Real path: /usr/share/man/man8/mount_nfs.8
Zurück

'\" te .\" Copyright (c) 1998, 2022, Oracle and/or its affiliates. .\" Copyright (c) 1989, AT&T. All rights reserved. .TH mount_nfs 8 "1 Feb 2022" "Oracle Solaris 11.4" "System Administration Commands" .SH NAME mount_nfs \- mount remote NFS resources .SH SYNOPSIS .LP .nf mount [-F nfs] [\fIgeneric_options\fR] [-o \fIspecific_options\fR] [-O] \fIresource\fR .fi .LP .nf mount [-F nfs] [\fIgeneric_options\fR] [-o \fIspecific_options\fR] [-O] \fImount_point\fR .fi .LP .nf mount [-F nfs] [\fIgeneric_options\fR] [-o \fIspecific_options\fR] [-O] \fIresource\fR \fImount_point\fR .fi .SH DESCRIPTION .sp .LP The \fBmount\fR utility attaches a named \fIresource\fR to the file system hierarchy at the pathname location \fImount_point\fR, which must already exist. If \fImount_point\fR has any contents prior to the \fBmount\fR operation, the contents remain hidden until the \fIresource\fR is once again unmounted. .sp .LP \fBmount_nfs\fR starts the \fBlockd\fR(8) and \fBstatd\fR(8) daemons if they are not already running. .sp .LP If the resource is listed in the \fB/etc/vfstab\fR file, the command line can specify either \fIresource\fR or \fImount_point\fR, and \fBmount\fR consults \fB/etc/vfstab\fR for more information. If the \fB-F\fR option is omitted, \fBmount\fR takes the file system type from \fB/etc/vfstab\fR. .sp .LP If the resource is not listed in the \fB/etc/vfstab\fR file, then the command line must specify both the \fIresource\fR and the \fImount_point\fR. .sp .LP \fIhost\fR can be an IPv4 or IPv6 address string. As IPv6 addresses already contain colons, enclose \fIhost\fR in a pair of square brackets when specifying an IPv6 address string. Otherwise the first occurrence of a colon can be interpreted as the separator between the host name and path, for example, \fB[1080::8:800:200C:417A]:tmp/file\fR. See \fBinet\fR(4P) and \fBinet6\fR(4P). .sp .ne 2 .mk .na \fB\fIhost\fR:\fIpathname\fR\fR .ad .br .sp .6 .RS 4n Where \fIhost\fR is the name of the NFS server host, and \fIpathname\fR is the path name of the directory on the server being mounted. The path name is interpreted according to the server's path name parsing rules and is not necessarily slash-separated, though on most servers, this is the case. .RE .sp .ne 2 .mk .na \fB\fInfs\fR://\fIhost\fR[:\fIport\fR]/\fIpathname\fR\fR .ad .br .sp .6 .RS 4n This is an NFS URL and follows the standard convention for NFS URLs as described in \fINFS URL Scheme\fR, RFC 2224. See the discussion of URLs and the public option under \fBNFS FILE SYSTEMS\fR for a more detailed discussion. .RE .sp .ne 2 .mk .na \fB\fIhost\fR:\fIpathname\fR \fInfs\fR://\fIhost\fR[:\fIport\fR]/\fIpathname\fR\fR .ad .br .sp .6 .RS 4n \fIhost\fR:\fIpathname\fR is a comma-separated list of \fIhost\fR:\fIpathname\fR. .sp See the discussion of replicated file systems and failover under \fBNFS FILE SYSTEMS\fR for a more detailed discussion. .RE .sp .ne 2 .mk .na \fB\fIhostlist\fR \fIpathname\fR\fR .ad .br .sp .6 .RS 4n \fIhostlist\fR is a comma-separated list of hosts. .sp See the discussion of replicated file systems and failover under \fBNFS FILE SYSTEMS\fR for a more detailed discussion. .RE .sp .LP The \fBmount\fR command maintains a table of mounted file systems in \fB/etc/mnttab\fR, described in \fBmnttab\fR(5). .sp .LP \fBmount_nfs\fR supports both NFSv3 and NFSv4 mounts. The default NFS version is NFSv4. .SS "SMF Management" .sp .LP The NFS client service is managed by the Service Management Facility (SMF) under the following service identifier: .sp .in +2 .nf svc:/network/nfs/client:default .fi .in -2 .sp .LP Note - .sp .RS 2 .sp .LP The \fBnfs/client\fR service does not need to be enabled for manual mounts or when using \fBautofs\fR maps. The sole purpose of the \fBnfs/client\fR service is to mount the NFS filesystems that are listed in \fB/etc/vfstab\fR with the "mount at boot" field set to "yes". .RE .sp .LP See the \fBsmf\fR(7) man page for more information about SMF. Use the \fBsvcs\fR(1) command to query the status of the service. Administrative actions such as enabling, disabling, or restarting the service can be performed by using the \fBsvcadm\fR(8) command. .SH OPTIONS .sp .LP See \fBmount\fR(8) for the list of supported \fIgeneric_options\fR. See \fBshare_nfs\fR(8) for a description of server options. .sp .ne 2 .mk .na \fB\fB-o\fR \fIspecific_options\fR\fR .ad .br .sp .6 .RS 4n Set file system specific options according to a comma-separated list with no intervening spaces. .sp .ne 2 .mk .na \fB\fBacdirmax=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Hold cached attributes for no more than \fIn\fR seconds after directory update. The default value is \fB60\fR. .RE .sp .ne 2 .mk .na \fB\fBacdirmin=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Hold cached attributes for at least \fIn\fR seconds after directory update. The default value is \fB30\fR. .RE .sp .ne 2 .mk .na \fB\fBacl\fR | \fBnoacl\fR\fR .ad .br .sp .6 .RS 4n If \fBnoacl\fR is specified, then NFS client will not issue ACL-related RPCs using the NFS_ACL protocol. The default value is determined by the \fBclient_nfs23_acl\fR property, which can be changed using \fBsharectl\fR(8). This option is relevant only for NFSv3 or NFSv2 mounts; it is silently ignored for NFSv4. The \fBnoacl\fR option should only be used when no files in the specified resource have an ACL. .RE .sp .ne 2 .mk .na \fB\fBacregmax=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Hold cached attributes for no more than \fIn\fR seconds after file modification. The default value is \fB60\fR. .RE .sp .ne 2 .mk .na \fB\fBacregmin=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Hold cached attributes for at least \fIn\fR seconds after file modification. The default value is \fB3\fR. .RE .sp .ne 2 .mk .na \fB\fBactimeo=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Set \fImin\fR and \fImax\fR times for regular files and directories to \fIn\fR seconds. See "File Attributes," below, for a description of the effect of setting this option to \fB0\fR. .sp See "Specifying Values for Attribute Cache Duration Options," below, for a description of how \fBacdirmax\fR, \fBacdirmin\fR, \fBacregmax\fR, \fBacregmin\fR, and \fBactimeo\fR are parsed on a \fBmount\fR command line. .RE .sp .ne 2 .mk .na \fB\fBbg\fR | \fBfg\fR\fR .ad .br .sp .6 .RS 4n If the first attempt fails, retry in the background, or, in the foreground. The default is \fBfg\fR. .RE .sp .ne 2 .mk .na \fB\fBforcedirectio\fR | \fBnoforcedirectio\fR\fR .ad .br .sp .6 .RS 4n If \fBforcedirectio\fR is specified, then for the duration of the mount, forced direct I/O is used. If the filesystem is mounted using \fBforcedirectio\fR, data is transferred directly between client and server, with no buffering on the client. If the filesystem is mounted using \fBnoforcedirectio\fR, data is buffered on the client. \fBforcedirectio\fR is a performance option that is of benefit only in large sequential data transfers. The default behavior is \fBnoforcedirectio\fR. .RE .sp .ne 2 .mk .na \fB\fBgrpid\fR\fR .ad .br .sp .6 .RS 4n By default, the GID associated with a newly created file obeys the System V semantics; that is, the GID is set to the effective GID of the calling process. This behavior can be overridden on a per-directory basis by setting the set-GID bit of the parent directory; in this case, the GID of a newly created file is set to the GID of the parent directory (see \fBopen\fR(2) and \fBmkdir\fR(2)). Files created on file systems that are mounted with the \fBgrpid\fR option obeys BSD semantics independent of whether the set-GID bit of the parent directory is set; that is, the GID is unconditionally inherited from that of the parent directory. .RE .sp .ne 2 .mk .na \fB\fBhard\fR | \fBsoft\fR\fR .ad .br .sp .6 .RS 4n Continue to retry requests until the server responds (\fBhard\fR) or give up and return an error (\fBsoft\fR). The default value is \fBhard\fR. Note that NFSv4 clients do not support soft mounts. If a user specifies soft option for NFSv4 mount, this mount option is silently ignored. .RE .sp .ne 2 .mk .na \fB\fBintr\fR | \fBnointr\fR\fR .ad .br .sp .6 .RS 4n Allow (do not allow) keyboard interrupts to kill a process that is hung while waiting for a response on a hard-mounted file system. The default is \fBintr\fR, which makes it possible for clients to interrupt applications that can be waiting for a remote mount. .RE .sp .ne 2 .mk .na \fB\fBllock\fR\fR .ad .br .sp .6 .RS 4n Use local locking (no lock manager). Note that this is a private interface. .RE .sp .ne 2 .mk .na \fB\fBnoac\fR\fR .ad .br .sp .6 .RS 4n Suppress data and attribute caching. The data caching that is suppressed is the write-behind. The local page cache is still maintained, but data copied into it is immediately written to the server. .RE .sp .ne 2 .mk .na \fB\fBnocto\fR\fR .ad .br .sp .6 .RS 4n Do not perform the normal close-to-open consistency. When a file is closed, all modified data associated with the file is flushed to the server and not held on the client. When a file is opened the client sends a request to the server to validate the client's local caches. This behavior ensures a file's consistency across multiple NFS clients. When \fBnocto\fR is in effect, the client does not perform the flush on close and the request for validation, allowing the possibility of differences among copies of the same file as stored on multiple clients. .sp This option can be used where it can be guaranteed that accesses to a specified file system are made from only one client and only that client. Under such a condition, the effect of \fBnocto\fR can be a slight performance gain. .RE .sp .ne 2 .mk .na \fB\fBnommaplockcheck\fR\fR .ad .br .sp .6 .RS 4n Bypass the memory mapping/locking check. Normally, the client checks for combinations of \fBmmap\fR(2) and \fBfcntl\fR(2) calls that could lead to file corruption. The \fBnommaplockcheck\fR option disables those checks. It should only be used when it can be guaranteed that mapped-file I/O, which involves whole pages whether or not the entire page is locked, will not conflict with byte-range locks held by other clients. .RE .sp .ne 2 .mk .na \fB\fBport=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n The server IP port number. The default is \fBNFS_PORT\fR. If the \fBport\fR option is specified, and if the resource includes one or more NFS URLs, and if any of the URLs include a \fBport\fR number, then the \fBport\fR number in the option and in the URL must be the same. .RE .sp .ne 2 .mk .na \fB\fBposix\fR\fR .ad .br .sp .6 .RS 4n Request POSIX.1 semantics for the file system. Requires a mount version 2 \fBmountd\fR(8) on the server. See \fBstandards\fR(7) for information regarding POSIX. .RE .sp .ne 2 .mk .na \fB\fBproto=\fR\fInetid\fR | \fBrdma\fR\fR .ad .br .sp .6 .RS 4n By default, the transport protocol that the NFS mount uses is the first available RDMA transport supported both by the client and the server. If no RDMA transport is found, then it attempts to use a TCP transport or, failing that, a UDP transport, as ordered in the \fB/etc/netconfig\fR file. If it does not find a connection oriented transport, it uses the first available connectionless transport. .sp Use this option to override the default behavior. .sp \fBproto\fR is set to the value of \fInetid\fR or \fBrdma\fR. \fInetid\fR is the value of the \fBnetwork_id\fR field entry in the \fB/etc/netconfig\fR file. .sp The UDP protocol is not supported for NFS version 4. If you specify a UDP protocol with the \fBproto\fR option, NFS version 4 is not used. .sp The RDMA transport is only supported in global zones and kernel zones. It is not supported within non-global zones. .RE .sp .ne 2 .mk .na \fB\fBpublic\fR\fR .ad .br .sp .6 .RS 4n The \fBpublic\fR option forces the use of the public file handle when connecting to the NFS server. The resource specified might not have an NFS URL. See the discussion of URLs and the public option under \fBNFS FILE SYSTEMS\fR for a more detailed discussion. .RE .sp .ne 2 .mk .na \fB\fBquota\fR | \fBnoquota\fR\fR .ad .br .sp .6 .RS 4n Enable or prevent \fBquota\fR(8) to check whether the user is over quota on this file system; if the file system has \fBquota\fR enabled on the server, \fBquota\fR(8) checks a file system only if the \fBquota\fR mount option is also set on the NFS client. .RE .sp .ne 2 .mk .na \fB\fBremount\fR\fR .ad .br .sp .6 .RS 4n Remounts a read-only file system as read-write (using the \fBrw\fR option). This option cannot be used with other \fB-o\fR options, and this option works only on currently mounted read-only file systems. .RE .sp .ne 2 .mk .na \fB\fBretrans=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Set the number of NFS retransmissions to \fIn\fR. The default value is \fB5\fR. For connection-oriented transports, this option has no effect because it is assumed that the transport performs retransmissions on behalf of NFS. .RE .sp .ne 2 .mk .na \fB\fBretry=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n The number of times to retry the \fBmount\fR operation. The default for the \fBmount\fR command is \fB10000\fR. .sp The default for the automounter is \fB0\fR, in other words, do not retry. You might find it useful to increase this value on heavily loaded servers, where automounter traffic is dropped, causing unnecessary server not responding errors. .RE .sp .ne 2 .mk .na \fB\fBrsize=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Set the read buffer size to a maximum of \fIn\fR bytes. The default value is \fB1048576\fR when using connection-oriented transports with version 3 or version 4 of the NFS protocol, and \fB32768\fR when using connection-less transports. The default can be negotiated down if the server prefers a smaller transfer size. "\fBRead\fR" operations may not necessarily use the maximum buffer size. When using version 2, the default value is \fB32768\fR for all transports. If a value lower than a system-defined minimum is specified, it is replaced by the minimum value (currently 1024). However, a server will be able to negotiate a transfer size that is smaller than the minimum. .RE .sp .ne 2 .mk .na \fB\fBsec=\fR\fImode\fR\fR .ad .br .sp .6 .RS 4n Set the security \fImode\fR for NFS transactions. If \fBsec=\fR is not specified, then the default action is to use \fBAUTH_SYS\fR over NFS version 2 mounts, use a user-configured default \fBauth\fR over NFS version 3 mounts, or to negotiate a mode over version 4 mounts. .sp The preferred mode for NFS version 3 mounts is the default mode specified in \fB/etc/nfssec.conf\fR (see \fBnfssec.conf\fR(5)) on the client. If there is no default configured in this file or if the server does not export using the client's default mode, then the client picks the first mode that it supports in the array of modes returned by the server. These alternatives are limited to the security flavors listed in \fB/etc/nfssec.conf\fR. .sp NFS version 4 mounts negotiate a security mode when the server returns an array of security modes. The client attempts the mount with each security mode, in order, until one is successful. .sp Only one mode can be specified with the \fBsec=\fR option. See \fBnfssec\fR(7) for the available \fImode\fR options. .RE .sp .ne 2 .mk .na \fB\fBtimeo=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Sets the NFS timeout to \fIn\fR tenths of a second. This value is primarily useful for connectionless transports, where manual tuning may be useful to improve performance. The default value is \fB11\fR tenths of a second for connectionless transports. .sp This value has no effect when using an RDMA transport. .sp For connection-oriented transports, the default value is \fB600\fR tenths of a second. There is usually no need to change this value because the underlying transport will manage its own retransmissions. One exception is replicated file systems, where a smaller timeout can improve failover performance. .RE .sp .ne 2 .mk .na \fB\fBvers=\fR\fINFS version number\fR\fR .ad .br .sp .6 .RS 4n Specifies the version of the NFS protocol to use for mounting. The valid versions for this option are 2, 3, 4, 4.0, and 4.1. .sp If you do not specify this option, the version used between the client and the server is the highest version available on both the systems. If the NFS server does not support the client's default maximum, the next lower version is considered until a matching version is found. .sp The default maximum version for a client is 4 which can result in either 4.0 or 4.1 mounts depending on the server. This value can be changed by setting the \fBclient_versmax\fR property. For more information see the \fBsharectl\fR(8) man page. .RE .sp .ne 2 .mk .na \fB\fBwsize=\fR\fIn\fR\fR .ad .br .sp .6 .RS 4n Sets the write buffer size to a maximum of \fIn\fR bytes. The default value is \fB1048576\fR when using connection-oriented transports with version 3 or version 4 of the NFS protocol, and \fB32768\fR when using connection-less transports. The default can be negotiated down if the server prefers a smaller transfer size. "\fBWrite\fR" operations may not necessarily use the maximum buffer size. When using version 2, the default value is \fB32768\fR for all transports. If a value lower than a system-defined minimum is specified, it is replaced by the minimum value (currently 1024). However, a server will be able to negotiate a transfer size that is smaller than the minimum. .RE .sp .ne 2 .mk .na \fB\fBxattr\fR | \fBnoxattr\fR\fR .ad .br .sp .6 .RS 4n Allows or disallows the creation and manipulation of extended attributes. The default is \fBxattr\fR. See \fBfsattr\fR(7) for a description of extended attributes. .RE .RE .sp .ne 2 .mk .na \fB\fB-O\fR\fR .ad .br .sp .6 .RS 4n Overlays mount. Allows the file system to be mounted over an existing mount point, making the underlying file system inaccessible. If a mount is attempted on a pre-existing mount point without setting this flag, the mount fails, producing the error "device busy." .RE .sp .ne 2 .mk .na \fB\fBidmap\fR\fR .ad .br .sp .6 .RS 4n By default, this option is not used during the mount. If the \fBidmap\fR mount option is not used, \fBAUTH_SYS\fR authentication is based on the equality between the client supplied UID/GID in the RPC credential and UID/GID stored in NFS server. In effect, it disables the \fBnfsmapid\fR functionality, which can make migration from legacy NFSv2/v3 systems to NFSv4 easier. NFS clients will automatically detect the servers which do not support numeric string uids and gids and automatically fall back to \fIuser@domain\fR format. .sp You can turn off this behavior, that is, turning off numeric strings uids and gids support, by using the mount option \fBidmap\fR. .RE .SH NFS FILE SYSTEMS .sp .ne 2 .mk .na \fBHard versus Soft\fR .ad .br .sp .6 .RS 4n File systems that are mounted read-write or that contain executable files should always be mounted with the \fBhard\fR option. Applications using \fBsoft\fR mounted file systems can incur unexpected I/O errors, file corruption, and unexpected program core dumps. The soft option is not recommended. .RE .sp .ne 2 .mk .na \fBAuthenticated requests\fR .ad .br .sp .6 .RS 4n The server can require authenticated NFS requests from the client. See \fBnfssec\fR(7). .RE .sp .ne 2 .mk .na \fBURLs and the public option\fR .ad .br .sp .6 .RS 4n If the \fBpublic\fR option is specified, or if the \fIresource\fR includes an NFS URL, \fBmount\fR attempts to connect to the server using the public file handle lookup protocol. See \fIWebNFS Client Specification\fR, RFC 2054. If the server supports the public file handle, the attempt is successful; \fBmount\fR does not need to contact the server's \fBrpcbind\fR(8) daemon to get the port number of the \fBmount\fR server and contact the \fBmountd\fR(8) daemon to get the initial file handle of \fIpathname\fR. If the NFS client and server are separated by a firewall that allows all outbound connections through specific ports, such as \fBNFS_PORT\fR, then NFS operations are enabled through the firewall. The public option and the NFS URL can be specified independently or together. They interact as specified in the following matrix: .sp .sp .TS tab( ) box; lw(1.65i) |lw(1.92i) |lw(1.92i) lw(1.65i) |lw(1.92i) |lw(1.92i) . \ \fIhost\fR:\fIpathname\fR NFS URL _ public option T{ Force public file handle and fail mount if not supported. T} T{ Force public file handle and fail mount if not supported. T} _ \ Use Native paths. Use Canonical paths. _ default Use \fBMOUNT\fR protocol. T{ Try public file handle with Canonical paths. If not supported, fail back to \fBMOUNT\fR protocol. T} .TE .sp A Native path is a path name that is interpreted according to conventions used on the native operating system of the NFS server. A Canonical path is a path name that is interpreted according to the URL rules. See \fIUniform Resource Locators (URL)\fR, RFC 1738. See "Examples," below, for uses of Native and Canonical paths. .RE .sp .ne 2 .mk .na \fBReplicated file systems and failover\fR .ad .br .sp .6 .RS 4n \fIresource\fR can list multiple read\(mionly file systems to be used to provide data. These file systems should contain equivalent directory structures and identical files. The file systems can be specified either with a comma\(miseparated list of \fIhost:/pathname\fR entries and/or NFS URL entries, or with a comma \(miseparated list of hosts, if all file system names are the same. If multiple file systems are named and the first server in the list is down, failover uses the next alternate server to access files. If the read\(mionly option is not chosen, replication is disabled. File access, for NFS versions 2 and 3, is blocked on the original if NFS locks are active for that file. .RE .SS "File Attributes" .sp .LP To improve NFS read performance, files and file attributes are cached. File modification times get updated whenever a write occurs. However, file access times can be temporarily out-of-date until the cache gets refreshed. .sp .LP The attribute cache retains file attributes on the client. Attributes for a file are assigned a time to be flushed. If the file is modified before the flush time, then the flush time is extended by the time since the last modification (under the assumption that files that changed recently are likely to change soon). There is a minimum and maximum flush time extension for regular files and for directories. Setting \fBactimeo=\fR\fIn\fR sets flush time to \fIn\fR seconds for both regular files and directories. .sp .LP Setting \fBactimeo=0\fR disables attribute caching on the client. This means that every reference to attributes is satisfied directly from the server though file data is still cached. While this guarantees that the client always has the latest file attributes from the server, it has an adverse effect on performance through additional latency, network load, and server load. .sp .LP Setting the \fBnoac\fR option also disables attribute caching, but has the further effect of disabling client write caching. While this guarantees that data written by an application is written directly to a server, where it can be viewed immediately by other clients, it has a significant adverse effect on client write performance. Data written into memory-mapped file pages (\fBmmap\fR(2)) are not written directly to this server. .SS "Specifying Values for Attribute Cache Duration Options" .sp .LP The attribute cache duration options are \fBacdirmax\fR, \fBacdirmin\fR, \fBacregmax\fR, \fBacregmin\fR, and \fBactimeo\fR, as described under OPTIONS. A value specified for \fBactimeo\fR sets the values of all attribute cache duration options except for any of these options specified following \fBactimeo\fR on a \fBmount\fR command line. For example, consider the following command: .sp .in +2 .nf example# mount -o acdirmax=10,actimeo=1000 server:/path /localpath .fi .in -2 .sp .sp .LP Because \fBactimeo\fR is the last duration option in the command line, its value (\fB1000\fR) becomes the setting for all of the duration options, including \fBacdirmax\fR. Now consider: .sp .in +2 .nf example# mount -o actimeo=1000,acdirmax=10 server:/path /localpath .fi .in -2 .sp .sp .LP Because the \fBacdirmax\fR option follows \fBactimeo\fR on the command line, it is assigned the value specified (\fB10\fR). The remaining duration options are set to the value of \fBactimeo\fR (\fB1000\fR). .SH EXAMPLES .LP \fBExample 1\fR Mounting an NFS File System .sp .LP To mount an NFS file system: .sp .in +2 .nf # \fBmount serv:/usr/src /usr/src\fR .fi .in -2 .sp .sp .LP This is an example of the use of a native path. .LP \fBExample 2\fR Mounting An NFS File System Read-Only With No suid Privileges .sp .LP To mount an NFS file system read-only with no suid privileges: .sp .in +2 .nf # \fBmount -r -o nosuid serv:/usr/src /usr/src\fR .fi .in -2 .sp .LP \fBExample 3\fR Mounting An NFS File System Over Version 2, with the UDP Transport .sp .LP To mount an NFS file system over version 2, with the UDP transport: .sp .in +2 .nf # \fBmount -o vers=2,proto=udp serv:/usr/src /usr/src\fR .fi .in -2 .sp .LP \fBExample 4\fR Mounting an NFS File System Using An NFS URL .sp .LP To mount an NFS file system using an NFS URL (a canonical path): .sp .in +2 .nf # \fBmount nfs://serv/usr/man /usr/man\fR .fi .in -2 .sp .LP \fBExample 5\fR Mounting An NFS File System Forcing Use Of The Public File Handle .sp .LP To mount an NFS file system and force the use of the public file handle and an NFS URL (a canonical path) that has a non 7-bit ASCII escape sequence: .sp .in +2 .nf # \fBmount -o public nfs://serv/usr/%A0abc /mnt/test\fR .fi .in -2 .sp .LP \fBExample 6\fR Mounting an NFS File System Using a Native Path .sp .LP To mount an NFS file system using a native path (where the server uses colons (:) as the component separator) and the public file handle: .sp .in +2 .nf # \fBmount -o public serv:C:doc:new /usr/doc\fR .fi .in -2 .sp .LP \fBExample 7\fR Mounting a Replicated Set of NFS File Systems with the Same Pathnames .sp .LP To mount a replicated set of NFS file systems with the same pathnames: .sp .in +2 .nf # \fBmount serv\(mia,serv\(mib,serv\(mic:/usr/man /usr/man\fR .fi .in -2 .sp .LP \fBExample 8\fR Mounting a Replicated Set of NFS File Systems with Different Pathnames .sp .LP To mount a replicated set of NFS file systems with different pathnames: .sp .in +2 .nf # \fBmount serv\(mix:/usr/man,serv\(miy:/var/man,nfs://serv-z/man /usr/man\fR .fi .in -2 .sp .SH FILES .sp .ne 2 .mk .na \fB\fB/etc/mnttab\fR\fR .ad .br .sp .6 .RS 4n Table of mounted file systems .RE .sp .ne 2 .mk .na \fB\fB/etc/dfs/fstypes\fR\fR .ad .br .sp .6 .RS 4n Default distributed file system type .RE .sp .ne 2 .mk .na \fB\fB/etc/vfstab\fR\fR .ad .br .sp .6 .RS 4n Table of automatically mounted resources .RE .SH ATTRIBUTES .sp .LP See \fBattributes\fR(7) for descriptions of the following attributes: .sp .TS tab( ) box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) . ATTRIBUTE TYPE ATTRIBUTE VALUE _ Availability \fBsystem/file-system/nfs\fR .TE .sp .SH SEE ALSO .sp .LP \fBmkdir\fR(2), \fBmmap\fR(2), \fBmount\fR(2), \fBopen\fR(2), \fBumount\fR(2), \fBlofs\fR(4FS), \fBinet\fR(4P), \fBinet6\fR(4P), \fBmnttab\fR(5), \fBnfssec.conf\fR(5), \fBattributes\fR(7), \fBfsattr\fR(7), \fBnfssec\fR(7), \fBstandards\fR(7), \fBlockd\fR(8), \fBmount\fR(8), \fBmountall\fR(8), \fBmountd\fR(8), \fBnfsd\fR(8), \fBquota\fR(8), \fBsharectl\fR(8), \fBstatd\fR(8) .sp .LP \fIManaging Network File Systems in Oracle Solaris 11.4\fR .sp .LP Callaghan, Brent, \fIWebNFS Client Specification\fR, RFC 2054, October 1996. .sp .LP Callaghan, Brent, \fINFS URL Scheme\fR, RFC 2224, October 1997. .sp .LP Berners-Lee, Masinter & McCahill, \fIUniform Resource Locators (URL)\fR, RFC 1738, December 1994. .SH NOTES .sp .LP An NFS server should not attempt to use NFS to mount the file systems it serves, unless they are provided by \fBzfs\fR(4FS). For an alternative to NFS mounts of file systems from the same host, see the \fBlofs\fR(4FS) man page. .sp .LP If the directory on which a file system is to be mounted is a symbolic link, the file system is mounted on \fBthe directory to which the symbolic link refers,\fR rather than being mounted on top of the symbolic link itself. .sp .LP SunOS 4.x used the \fBbiod\fR maintenance procedure to perform parallel read-ahead and write-behind on NFS clients. SunOS 5.x made \fBbiod\fR obsolete with multi-threaded processing, which transparently performs parallel read-ahead and write-behind. .sp .LP Since the root \fB(\fR/\fB)\fR file system is mounted read-only by the kernel during the boot process, only the \fBremount\fR option (and options that can be used in conjunction with \fBremount\fR) affect the root (\fB/\fR) entry in the \fB/etc/vfstab\fR file.