Date: Mon, 2 Mar 2020 22:28:19 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: alan somers <asomers@gmail.com>, freebsd-fs <freebsd-fs@freebsd.org> Cc: Rick Macklem <rmacklem@freebsd.org> Subject: Re: go build, flock, and NFS_BADSEQID Message-ID: <YTBPR01MB33740785F12E0D2216F4AA28DDE70@YTBPR01MB3374.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <CAOtMX2gsSzpNgBCarT1xP4bD6e4SiN_Qo-RjpuogSjb1SWZBRA@mail.gmail.com> References: <CAOtMX2gsSzpNgBCarT1xP4bD6e4SiN_Qo-RjpuogSjb1SWZBRA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Try "minorversion=3D1". 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@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 se= rver is running 12.0-RELEASE and the client is running 12.1-RELEASE. But t= he build reliably fails because flock(2) returns EACCES. Dtrace shows the = cause is nfsrpc_advlock returning NFS_BADSEQID. This sounds like an NFS bu= g (server, client, or both? I'm not sure). I'm not an NFS expert. Is thi= s something I should pursue, and would somebody please give me advise on ho= w to debug further? -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTBPR01MB33740785F12E0D2216F4AA28DDE70>