go build, flock, and NFS_BADSEQID

Alan Somers asomers at freebsd.org
Mon Mar 2 22:40:47 UTC 2020

Is that a mount option?  Because it seems like I can't set it with "mount
-u".  Do I need to completely unmount first?

On Mon, Mar 2, 2020 at 3:28 PM Rick Macklem <rmacklem at uoguelph.ca> wrote:

> Try "minorversion=1". The seqid stuff is NFSv4.0 specific and shouldn't
> be broken, but NFSv4.1 fixed all this in better ways.
> rick
> ________________________________________
> From: alan somers <asomers at gmail.com>
> Sent: Monday, March 2, 2020 2:31 PM
> To: freebsd-fs
> 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?
> -Alan

More information about the freebsd-fs mailing list