rpc.umntall error on boot

[Rick Macklem]

Robert Simmons wrote:
> I'm getting the following error on a new install with NFS:
> 
> kernel: rpc.umntall:
> kernel: fileserver: MOUNTPROG: RPC: Program not registered
> kernel:
> kernel: rpc.umntall:
> kernel: localhost: MOUNTPROG: RPC: Program not registered
> kernel:
> kernel: rpc.umntall:
> kernel: fileserver: MOUNTPROG: RPC: Program not registered
> 
> My /etc/rc.conf contains the following:
> nfs_server_enable="YES"
> nfs_client_enable="YES"
> rpcbind_enable="YES"
> 
Well, if your server isn't also a client (doesn't do mounts from
other NFS servers), you can just set
   nfs_client_enable="NO"

and the message will go away.

Otherwise, I don't know how to get rid of it, but it's pretty harmless.
What happens is that /etc/rc.d/nfsclient is executed before
/etc/rc.d/mountd. It finds /var/db/mountdtab non-empty and tries to
get a port from rpcbind for mountd. Since mountd isn't running yet,
so it fails. Since telling the server on the same machine to clear
out /var/db/mountdtab for the client is basically meaningless, failing
shouldn't be a problem.

Although mountd maintains /var/db/mountdtab, it is only used for
replying to "showmount" and doesn't affect the function of actual
mounts. (The NFS protocol really has no concept of a "mount".
The unmount RPC for the mountd protocol just updates /var/db/mountdtab
and doesn't affect NFS.) rpc.umntall is just meant to clean up
/var/db/mountdtab after a client reboot.

rick
> and /etc/exports is the following (for testing):
> /storage -maproot=root 127.0.0.1
> 
> Even if I run the NFSv4 experimental server that does not use rpcbind
> (so I set it ="NO"), the error is still there.
> 
> This problem does not seem to affect mounting or NFS functions. What
> could be causing this error?
> 
> Rob
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"