FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F13.3 2023-10-24T18:13:18Z 2023-10-24T18:13:18Z John Baldwin jhb@FreeBSD.org 2023-09-25T14:54:56Z urn:sha1:de270f81b246e154640c0d250696c458ff1c0e3b These do not use __FBSDID but instead use bare char arrays. Reviewed by: imp, emaste Differential Revision: https://reviews.freebsd.org/D41957 (cherry picked from commit eba230afba4932f02a1ca44efc797cf7499a5cb0) 2023-05-24T02:15:01Z Rick Macklem rmacklem@FreeBSD.org 2023-02-22T22:09:15Z urn:sha1:8d92ebe2fa49f6701e6aea7345b9ab9047aaec5b For the cases where the nfsd(8) daemon is already running or has failed to start within a prison due to an incorrect prison configuration, the failure message logged is: Can't read stable storage file: operation not permitted This patch replaces the above with more meaningful messages. It depends on commit 10dff9da9748 to differentiate between the above two cases, however even without this commit, the messages should be an improvement. (cherry picked from commit fe5c211ba87315b098769a7e6d50b41f00f6fed4) 2021-04-15T21:34:24Z Rick Macklem rmacklem@FreeBSD.org 2021-04-01T22:09:03Z urn:sha1:33c839b6f6798011d87ad26b43c66f4ce04cdc2c An NFSv4 only configuration does not register with rpcbind(). Without this patch a failure to rpcb_unset() is reported when the daemon is terminated for this case. This is harmless noise, but this patch avoids calling rpcb_unset() for the NFSv4 only case, avoiding the noise. When called with "-d", it still does the rpcb_unset(), assuming that the configuration might have been changed to NFSv4 only and unregistering with rpcbind() might still be needed. (cherry picked from commit b43fe9eb4b3365156016ae3477747a46fc094bb8) 2019-02-21T22:49:39Z Sean Eric Fagan sef@FreeBSD.org 2019-02-21T22:49:39Z urn:sha1:c0ca37d17b451f3eedbb95041475280b721451a7 Specifically, I put the new option line in the wrong place, and then fixed up the rest without realizing it. This puts the usage statement back to what it was, with an additional line for the new -V option. Reported by: mav Sponsored by: iXsystems Inc. 2019-02-16T00:15:54Z Sean Eric Fagan sef@FreeBSD.org 2019-02-16T00:15:54Z urn:sha1:025816d9cecee9c9dc18bd4ef46b6ed7554d6cfc Specifically, this allows (via "-V vhostname") telling nfsd what principal to use, instead of the hostname. This is used at iXsystems for fail-over in HA systems. Reviewed by: macklem Sponsored by: iXsystems Inc. Differential Revision: https://reviews.freebsd.org/D19191 2018-11-04T06:39:01Z Baptiste Daroussin bapt@FreeBSD.org 2018-11-04T06:39:01Z urn:sha1:56b187fca866ca67ff22b9f39b7c55430693d58d Factorize code by using struct sockaddr_storage to handle both ipv6 and ipv4 Discussed with: rmacklem Reviewed by: manu MFC after: 1 month Sponsored by: Gandi.net Differential Revision: https://reviews.freebsd.org/D13223 2018-07-27T23:10:28Z Rick Macklem rmacklem@FreeBSD.org 2018-07-27T23:10:28Z urn:sha1:35f38de3c9e29f26df89dae34cbf8da31057d391 This patch adds code to handle IPv6 addresses returned by getaddrinfo() for the host entries in the "-p" command line argument. If the IPv6 address is a link local address, only use it if it is the only address for the host. This is done since there is no way to know if the NFSv4.1 pNFS client is in the same scope zone as the MDS. inet_ntop() is used for the IPv6 address translation, since the client will have no use for the scope zone suffix and inet_ntop() does not put this in the address string. Discussed with: bu7cher@yandex.ru 2018-07-02T19:26:31Z Rick Macklem rmacklem@FreeBSD.org 2018-07-02T19:26:31Z urn:sha1:ed464272682458513eda8bead84797eb5b629a96 Without this patch, the pNFS server distributes the data storage files across all of the specified DSs. A tester noted that it would be nice if a system administrator could control which DSs are used to store the file data for a given exported MDS file system. This patch adds an optional suffix for each entry in the "-p" option argument that specifies "store file data for this MDS file system" in this DS. The patch should only affect sites using the pNFS server (specified via the "-p" command line option for nfsd. The interface between the nfsd and the kernel has changed with this patch, so anyone using the "-p" option needs to rebuild their nfsd from sources with this patch applied to them. Discussed with: james.rose@framestore.com 2018-06-30T12:14:20Z Rick Macklem rmacklem@FreeBSD.org 2018-06-30T12:14:20Z urn:sha1:2f800e5593da7a7addda89f5b579ddaa7684d15c The kernel code assumes that nfsdargs.addr == NULL and nfsdargs.addrlen == 0 when there is no "-p" argument used for starting the nfsd. This small patch ensures this is the case. In practice, I believe this always happened, since "nfsdargs" was the last element on the stack for "main()", but this little patch ensures it will be the case. Spotted by inspection while adding a new optional field for "-p". 2018-06-14T20:36:55Z Rick Macklem rmacklem@FreeBSD.org 2018-06-14T20:36:55Z urn:sha1:61a835e4033489cc4c33b51dfeb80b14cd12265a The "-p" option specifies that the nfsd should run a pNFS service instead of a regular NFS service. The "-m" option is only meaningful when used with "-p" to specify that mirroring on the DSs should be done and on how many of them. This change requires the kernel changes committed as r334930. The man page update will be committed as a separate commit soon.