Re: rpc.lockd spinning; much breakage

On Tue, 13 May 2003, Andrew P. Lentvorski, Jr. wrote:

> On Tue, 13 May 2003, Robert Watson wrote:
> 
> > May 13 14:31:31 crash1 rpc.lockd: nlm_lock_res from 192.168.50.1
> > May 13 14:31:33 crash1 rpc.lockd: nlm_lock_res from 192.168.50.1
> > May 13 14:31:42 crash1 rpc.lockd: nlm_granted_msg from 192.168.50.1
> > May 13 14:31:42 crash1 rpc.lockd: nlm_unlock_res from 192.168.50.1
> > May 13 14:31:42 crash1 rpc.lockd: process 933: No such process
> > May 13 14:31:53 crash1 rpc.lockd: nlm_lock_res from 192.168.50.1
> 
> Why is everything logging nlm_blahblahblah instead of nlm4_blahblahblah? 
> This normally implies that you are running NFSv2.  Is that correct? 

I believe our diskless environment mounts using NFSv2 only, so my root
file system on this box uses NFSv2.  Recompiling nfs_diskless.c to use the
NFSv3 mount flag results in a panic due to getting EPROTONOSUPPORT when
looking for init(8), so I can only assume that's a bad idea. :-)  Could be
because the NFS handle for the root is passed from the boot loader as an
NFSv2 handle, which probably wouldn't happify NFSv3.  I'll try doing the
tests on NFSv3 file systems this evening.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert_at_fledge.watson.org      Network Associates Laboratories