Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 25 Mar 2012 15:35:43 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Christoph Egger <christoph@sieglitzhof.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: NFS locking and linux NFS server
Message-ID:  <20120325203542.GA55964@dan.emsphone.com>
In-Reply-To: <87zkb4lr1y.fsf@hepworth.siccegge.de>
References:  <87zkb4lr1y.fsf@hepworth.siccegge.de>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Mar 25), Christoph Egger said:
> Hi all!
> 
>   I have a Linux Host (2.6.32 kernel, Debian stable) providong NFS
> shares. Locking files on that share works fine for linux clients [0]
> while it fails on a freebsd 9.0-STABLE system. The interwebs indicate
> there have been problems witha buggy linux implementation back in 2006
> but no more hits for that problem in recent times so I assume it's
> fixed?
> 
> root@freebsd /mnt/
> 11:27 0 # kldstat -v | grep nfs
> 		341 nfscommon
> 		386 nfslockd
> 		344 nfsd
> 		385 nfssvc
> 		342 nfs
> 		343 nfscl
> 		384 nfslock
>                                                                                                                                                                                                                                                                                                                           
> root@freebsd /mnt/
> 11:28 0 # flock test -c ls
> flock: test: Operation not supported
> 
> root@freebsd /mnt/
> 11:31 0 # mount | grep nfs
> 10.70.255.8:/home/ on /mnt/ (nfs)

Are you running statd and lockd (in rc.conf, rpc_statd_enable="YES" and
rpc_lockd_enable="YES")?  Make sure that "rpcinfo localhost" and "rpcinfo
otherhost" both show "nlockmgr" and "status" services.

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120325203542.GA55964>