kern/50807: NFS file locking as client deos not working

Bruce Evans bde at zeta.org.au
Fri Apr 11 04:25:21 PDT 2003


On Fri, 11 Apr 2003, Shao Zhang wrote:

> >Description:
> 	When running the system as an NFS client, file locking does not work at
> all. The call to fcntl(id, F_SETLK, ...) returns errno 45. The nfs server used
> is a Redhat Linux 7, with kernel 2.4.2. I have verified that it works fine in
> both 4.5-RELEASE and 4.6-RELEASE. I have the following entries in my rc.conf:
>
> nfs_client_enable="YES"         # This host is an NFS client (or NO).
> nfs_access_cache="4"            # Client cache timeout in seconds
> nfs_server_enable="NO"          # This host is an NFS server (or NO).
> nfs_server_flags="-u -t -n 4"   # Flags to nfsd (if enabled).
> nfs_privport="YES"              # Provide NFS only on secure port (or NO).
> nfs_bufpackets="DEFAULT"        # bufspace (in packets) for client (or DEFAULT)

At least for a -current server and client, one or both rpc.lockd and
rpc.statd enabled here on one or both of the client and server.  IIRC,
enabling both on both works but may be more than necessary.  rc.conf.5
is very unclear on the exact servers required.  mount_nfs.8 gives more
details in connection with how to not use these servers (-L/nolockd flag)
but is also unclear.

RELENG_4 fakes nfs locking so that lock requests succeed but don't actually
work.  "mount -t nfs -onolockd ..." gives the same fake locking as in
RELENG_4.

Bruce


More information about the freebsd-bugs mailing list