NFS(4) File Formats and Configurations NFS(4) NNAAMMEE nnffss - NFS configuration properties DDEESSCCRRIIPPTTIIOONN The behavior of the nfsd(1M), nfsmapid(1M), lockd(1M), and mountd(1M) daemons and mount_nfs(1M) command is controlled by property values that are stored in the Service Management Facility, smf(5). The sharectl(1M) command should be used to query or change values for these properties. Changes made to nnffss property values on the nnffssdd, lloocckkdd, mmoouunnttdd, or mmoouunntt__nnffss command line override the values set using sharectl(1M). The following list describes the properties: cclliieenntt__vveerrssmmiinn=_n_u_m cclliieenntt__vveerrssmmaaxx=_n_u_m The NFS client only uses NFS versions in the range specified by these properties. Valid values of versions are: 2, 3, and 4. Default minimum version is 2, while default maximum is 4. You can override this range on a per-mount basis by using the --oo vveerrss= option to mount_nfs(1M). sseerrvveerr__vveerrssmmiinn=_n_u_m sseerrvveerr__vveerrssmmaaxx=_n_u_m The NFS server only uses NFS versions in the range specified by these properties. Valid values of versions are: 2, 3, and 4. Default minimum version is 2, while the default maximum version is 4. sseerrvveerr__ddeelleeggaattiioonn=oonn|ooffff By default the NFS server provides delegations to clients. The user can turn off delegations for all exported filesystems by setting this variable to off. This variable only applies to NFS Version 4. nnffssmmaappiidd__ddoommaaiinn=[_s_t_r_i_n_g] By default, the nnffssmmaappiidd uses the DNS domain of the system. This setting overrides the default. This domain is used for identifying user and group attribute strings in the NFS Version 4 protocol. Clients and servers must match with this domain for operation to proceed normally. This variable only applies to NFS Version 4. See _S_e_t_t_i_n_g _n_f_s_m_a_p_i_d___d_o_m_a_i_n below for further details. mmaaxx__ccoonnnneeccttiioonnss=_n_u_m Sets the maximum number of concurrent, connection-oriented connections. The default is -1 (unlimited). Equivalent to the --cc option in nnffssdd. lliisstteenn__bbaacckklloogg=_n_u_m Set connection queue length for the NFS over a connection- oriented transport. The default value is 32, meaning 32 entries in the queue. Equivalent to the --ll option in nnffssdd. pprroottooccooll=[aallll|_p_r_o_t_o_c_o_l] Start nnffssdd over the specified protocol only. Equivalent to the --pp option in nnffssdd. aallll is equivalent to --aa on the nnffssdd command line. Mutually exlusive of ddeevviiccee. For the UDP protocol, only version 2 and version 3 service is established. NFS Version 4 is not supported for the UDP protocol. ddeevviiccee=[_d_e_v_n_a_m_e] Start NFS daemon for the transport specified by the given device only. Equivalent to the --tt option in nnffssdd. Mutually exclusive of pprroottooccooll. sseerrvveerrss=_n_u_m Maximum number of concurrent NFS requests. Equivalent to last numeric argument on the nnffssdd command line. The default is 1024. lloocckkdd__lliisstteenn__bbaacckklloogg=_n_u_m Set connection queue length for lloocckkdd over a connection-oriented transport. The default and minimum value is 32. lloocckkdd__sseerrvveerrss=_n_u_m Maximum number of concurrent lloocckkdd requests. The default is 256. lloocckkdd__rreettrraannssmmiitt__ttiimmeeoouutt=_n_u_m Retransmit timeout, in seconds, before lloocckkdd retries. The default is 5. ggrraaccee__ppeerriioodd=_n_u_m Grace period, in seconds, that all clients (both NLM and NFSv4) have to reclaim locks after a server reboot. This parameter also controls the NFSv4 lease interval. The default is 90. mmoouunnttdd__lliisstteenn__bbaacckklloogg=_n_u_m Set the connection queue length for mmoouunnttdd over a connection- oriented transport. The default value is 64. mmoouunnttdd__mmaaxx__tthhrreeaaddss=_n_u_m Maximum number of threads for mmoouunnttdd. The default value is 16. mmoouunnttdd__ppoorrtt=_n_u_m The IP port number on which mmoouunnttdd should listen. The default value is 0, which means it should use a default binding. ssttaattdd__ppoorrtt=_n_u_m The IP port number on which ssttaattdd should listen. The default value is 0, which means it should use a default binding. SSeettttiinngg nnffssmmaappiidd__ddoommaaiinn As described above, the setting for nnffssmmaappiidd__ddoommaaiinn overrides the domain used by nfsmapid(1M) for building and comparing outbound and inbound attribute strings, respectively. This setting overrides any other mechanism for setting the NFSv4 domain. In the absence of a nnffssmmaappiidd__ddoommaaiinn setting, the nfsmapid(1M) daemon determines the NFSv4 domain as follows: ++oo If a properly configured _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f (see resolv.conf(4)) exists, nnffssmmaappiidd queries specified nameserver(s) for the domain. ++oo If a properly configured _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f (see resolv.conf(4)) exists, but the queried nameserver does not have a proper record of the domain name, nnffssmmaappiidd attempts to obtain the domain name through the BIND interface (see resolver(3RESOLV)). ++oo If no _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f exists, nnffssmmaappiidd falls back on using the configured domain name (see domainname(1M)), which is returned with the leading domain suffix removed. For example, for widgets.sales.acme.com, sales.acme.com is returned. ++oo If _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f does not exist, no domain name has been configured (or no _/_e_t_c_/_d_e_f_a_u_l_t_d_o_m_a_i_n exists), nnffssmmaappiidd falls back on obtaining the domain name from the host name, if the host name contains a fully qualified domain name (FQDN). If a domainname is still not obtained following all of the preceding steps, nnffssmmaappiidd will have no domain configured. This results in the following behavior: ++oo Outbound "owner" and "owner_group" attribute strings are encoded as literal id's. For example, the UID 12345 is encoded as 12345. ++oo nnffssmmaappiidd ignores the "domain" portion of the inbound attribute string and performs name service lookups only for the user or group. If the user/group exists in the local system name service databases, then the proper uid/gid will be mapped even when no domain has been configured. This behavior implies that the same administrative user/group domain exists between NFSv4 client and server (that is, the same uid/gid's for users/groups on both client and server). In the case of overlapping id spaces, the inbound attribute string could potentially be mapped to the wrong id. However, this is not functionally different from mapping the inbound string to nnoobbooddyy, yet provides greater flexibility. SSEEEE AALLSSOO lockd(1M), mount_nfs(1M), mountd(1M), nfsd(1M), nfsmapid(1M), sharectl(1M), smf(5) NexentaStor December 18, 2016 NexentaStor