Hi
mefizto,
you already marked the thread as "Solved", I hope you have no objection when I continue to provide some more information regarding the minimal necessary configuring of a NFS on FreeBSD. You expressed in the other thread the need to understand the effect of a command before executing it (in this case configuration settings), and not following it blindly. The following explanation demonstrates why
nfs_server_enable is all it needs to configure a NFS(v3) server.
The most basic NFSv3 configuration (you have
touch /etc/exports, that means there is no V4: <rootdir> line for NFSv4 exports) is:
NFS server /etc/rc.conf:
zfs set sharenfs=on pool/dataset
Unfortunately the Handbook is not up to date with the current state of the systems capability.
consequently, I have in the server /etc/rc.conf:
Code:
rpcbind_enable="YES"
nfs_server_enable="YES"
# nfs_v4_server_enable="YES"
mountd_enable="YES"
mountd_flags="-r"
rpc_lockd_enable="YES"
rpc_statd_enable="YES"
rpcbind,
mountd and eventually
mountd_flags are not necessary.
Those variables in
/etc/rc.conf are On/Off (YES, NO), and other configuration parameter knobs for
rc.d (8)scripts under
/etc/rc.d (if scripts from packages/ports then also from
/usr/local/etc/rc.d).
Many of the
/etc/rc.d scripts need other scripts to run before or after running themself. Those are specified in the scripts REQUIRE and BEFORE
rcorder(8) keywords. When REQUIRE, all specified scripts (so called "conditions") in that line are started before the script itself is started.
After the above explanation it will be clearer why
rpcbind,
mountd and eventually
mountd_flags variables are unnecessary.
mountd_enable="YES" doesn't need to be set,
nfs_server_enable="YES" calls
/etc/rc.d/nfsd, which starts
/etc/rc.d/mountd automatically (# REQUIRE: mountcritremote
mountd hostname gssd nfsuserd)
mountd_flags="-r": The default is set as
mountd_flags="-r -S" in
/etc/defaults/rc.conf, set it if you want to override the default setting "-r -S". (See also
ps aux below.)
rpcbind_enable="YES" doesn't need to be set either.
/etc/rc.d/nfsd starts
/etc/rc.d/mountd, which starts
/etc/rc.d/rpcbind (
/etc/rc.d/mountd, # REQUIRE: NETWORKING
rpcbind quota).
To proof the above in a live system, checked in a
nfs_server_enable="YES" only, no
/etc/exports, ZFS sharenfs exported NFS server:
Code:
# ps aux | egrep 'nfsd|mountd|rpcbind'
root 722 0.0 0.6 12836 2612 - Ss 09:37 0:00.01 /usr/sbin/rpcbind
root 743 0.0 0.6 12892 2680 - Ss 09:37 0:00.57 /usr/sbin/mountd -r -S /etc/exports /etc/zfs/exports
root 745 0.0 0.5 12764 2532 - Is 09:37 0:00.03 nfsd: master (nfsd)
root 748 0.0 0.6 12764 2708 - S 09:37 0:00.01 nfsd: server (nfsd)
root 979 0.0 0.5 12848 2412 v4 S+ 10:05 0:00.00 egrep nfsd|mountd|rpcbind
The details of the above REQUIRE and other
rcorder(8) keywords can be looked in the just mentioned manual,
rc(8),
rc.subr(8),
Practical rc.d scripting in BSD.
To configure a NFSv4 FreeBSD server all is needed is to set
Code:
nfs_server_enable="YES"
nfsv4_server_enable="YES"
eventually
nfsuserd_enable="YES"
nfsv4(4)
On a FreeBSD NFS client, no configuration needed:
Id., re the Handbook. As such, I have in the client /etc/rc.conf:
Code:
nfs_client_enable="YES"
rpc_lockd_enable="YES"
rpc_statd_enable="YES"
Try to mount on the client without any rc.conf configuration.
As best as I can tell, the
mountd(8) will not start without the /etc/exports, regardless of the fact that the /etc/zfs/exports exists.
mountd(8) will start, regardless if
/etc/exports exist. At most it will complain about the missing file in the logs.
I don't see why your setup wouldn't work without a (empty) exports file, well, the important things is, it's working now.
