Matty wrote:
> I configured a new NFS share today with the sharemgr utility, and for
> some reason the settings are causing the nfs/server SMF service to
> fault. Here is the configuration I created:
>
> $ sharemgr show -vp
> default nfs=()
> zfs
> build nfs=() nfs:sys=(ro="192.168.1.0/24,anon=0")
> /bits/provisioning "Build infrastructure"
>
I think that share is wrong. You want an '@' in there to denote a subnet:
[th199096 at jhereg cleanup]> sudo share -F nfs -o r...@192.168.3 /tmp
[th199096 at jhereg cleanup]> sharemgr show -vp
default nfs=()
* /tmp nfs:sys=(rw="@192.168.3") ""
zfs
zfs/tank/builds nfs=(anon="0") nfs:sys=(rw="*")
/builds
/builds/th199096
/builds/th199096/cleanup
/builds/th199096/dedup
/builds/th199096/refclnt
/builds/th199096/refsrvr
/builds/th199096/stock
zfs/tank/tools nfs=() nfs:sys=(ro="*")
/tank/tools
/tank/tools/onbld-rsync
/tank/tools/onnv-tools-i386
But that isn't the problem....
> After rebooting my host, I noticed that the nfs/server SMF service
> goes into maintenance:
>
> $ svcs -vx
> svc:/network/nfs/server:default (NFS server)
> State: maintenance since Mon May 04 04:33:09 2009
> Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
> See: http://sun.com/msg/SMF-8000-KS
> See: man -M /usr/share/man -s 1M nfsd
> See: /var/svc/log/network-nfs-server:default.log
> Impact: This service is not running.
>
> And the following errors are displayed in the SMF server log:
>
> couldn't find netconfig entry for protocol 4Could not start NFS
> service for any protocol. Exitingrc=1
>
> Does anyone on the list happen to know what these errors means? I am
> running Nevada build 110 with all the default NFS settings.
>
> Thanks,
> - Ryan
> --
> http://prefetch.net
> _______________________________________________
> nfs-discuss mailing list
> nfs-discuss at opensolaris.org
>
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/fs.d/nfs/nfsd/nfsd.c#560
I don't understand this. If we look at the code:
557 (void) endnetconfig(nc);
558 if (protoFound == FALSE) {
559 fprintf(stderr,
560 "couldn't find netconfig entry for
protocol %s",
561 proto);
562 }
then we would expect to see the offending protocol listed in the server
log. '4' is not
what I would expect...
In your /etc/default/nfs file, is this changed?
# Start NFS daemon over the specified protocol only.
# Equivalent to -p, ALL is equivalent to -a on the nfsd command line.
# Mutually exclusive with NFSD_DEVICE.
NFSD_PROTOCOL=ALL
Hmm, and do you know what your command line options to start nfsd are?
I.e., that probably means has this file: /var/svc/manifest/network/nfs
been changed from
the default?
And in turn, that leads me to ask if this file is different from the
default?
/lib/svc/method/nfs-server
Ehh, you could also try making the share follow legal syntax and see if
that fixes things! :->
BTW: Quick survey, did you look at share_nfs(1M) for the network syntax?
If you did, was
it misleading. If you haven't, could you and respond about whether or
not the syntax worked
for you?
I.e., we are concerned that coverage isn't cutting it.
