Date: Mon, 2 Mar 2020 15:40:32 -0700 From: Alan Somers <asomers@freebsd.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-fs <freebsd-fs@freebsd.org>, Rick Macklem <rmacklem@freebsd.org> Subject: Re: go build, flock, and NFS_BADSEQID Message-ID: <CAOtMX2h1P4KeYU9otRSZp_c=ZeSUzB01G9KNGUiv26puOLeQjQ@mail.gmail.com> In-Reply-To: <YTBPR01MB33740785F12E0D2216F4AA28DDE70@YTBPR01MB3374.CANPRD01.PROD.OUTLOOK.COM> References: <CAOtMX2gsSzpNgBCarT1xP4bD6e4SiN_Qo-RjpuogSjb1SWZBRA@mail.gmail.com> <YTBPR01MB33740785F12E0D2216F4AA28DDE70@YTBPR01MB3374.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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@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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2h1P4KeYU9otRSZp_c=ZeSUzB01G9KNGUiv26puOLeQjQ>