go build, flock, and NFS_BADSEQID
rmacklem at uoguelph.ca
Mon Mar 2 22:28:24 UTC 2020
Try "minorversion=1". The seqid stuff is NFSv4.0 specific and shouldn't
be broken, but NFSv4.1 fixed all this in better ways.
From: alan somers <asomers at gmail.com>
Sent: Monday, March 2, 2020 2:31 PM
Cc: Rick Macklem
Subject: go build, flock, and NFS_BADSEQID
I'm trying to build a Go project with /usr/home mounted with NFSv4. The server is running 12.0-RELEASE and the client is running 12.1-RELEASE. But the build reliably fails because flock(2) returns EACCES. Dtrace shows the cause is nfsrpc_advlock returning NFS_BADSEQID. This sounds like an NFS bug (server, client, or both? I'm not sure). I'm not an NFS expert. Is this something I should pursue, and would somebody please give me advise on how to debug further?
More information about the freebsd-fs