FreeBSD v14.1-RELEASE-p3: NFSv3 - no lock available

Mount /usr/ports via NFSv3:
# lockf /usr/ports/UPDATING ls
lockf: cannot open /usr/ports/UPDATING: Permission denied

Another host:
# lockf /usr/ports/UPDATING ls
nfs server IP:/usr/ports: lockd not responding
nfs server IP/usr/ports: lockd not responding
nfs server IP:/usr/ports: lockd not responding
nfs server IP:/usr/ports: lockd not responding
nfs server IP:/usr/ports: lockd not responding
nfs server IP:/usr/ports: lockd not responding
nfs server IP:/usr/ports: lockd not responding
nfs server IP:/usr/ports: lockd not responding
nfs server IP:/usr/ports: lockd not responding
lockf: cannot open /usr/ports/UPDATING: Invalid argument

Server and both clients are FreeBSD 14.1-p6 amd64.

# nfsstat -m
IP:/usr/ports on /usr/ports
nfsv3,tcp,resvport,nconnect=1,soft,intr,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=1048576,wsize=1048576,readdirsize=1048576,readahead=16,wcommitsize=16777216,timeout=120,retrans=2

Add nolockd to mount options can be used as workaround.
 
i'm having same issue on 13. so nfs locks don't work on 13 at all? when did they work? i mean it once had, right? if indeed nfsv3 locks can't be used at all, how come such bug even went in? please don't tell that nfsv3 locks are only used by 0.001% people and therefore it's rarely used feature that's never tested? tell me it's not true eh
 
You must log in or register to reply here.
Back
Top