Date: Wed, 30 Dec 2020 02:02:48 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Cc: Konstantin Belousov <kib@FreeBSD.org>, Alan Somers <asomers@freebsd.org>, Kirk McKusick <mckusick@mckusick.com>, Mark Johnston <markj@freebsd.org> Subject: r367672 broke the NFS server Message-ID: <YQXPR0101MB0968DC349AFD081480768028DDD70@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
next in thread | raw e-mail | index | archive | help
Hi,=0A=
=0A=
Post r367671...=0A=
When multiple files are being created by an NFS client in the same=0A=
directory, the VOP_CREATE()/ufs_create() can fail with ERELOOKUP.=0A=
This results in a EIO return to the NFS client.=0A=
--> This causes "nfsv4 client/server protocol prob err=3D10026"=0A=
on the client for NFSv4.0 mounts.=0A=
--> This explains why this error has been reported by=0A=
several people lately, although it should "never happen".=0A=
=0A=
Unfortunately, for the NFS server, the Lookup call is done separately=0A=
and it will not be easy to redo it, given the current NFS code structure.=
=0A=
=0A=
Is there another way to deal with the problem r367672 was fixing that=0A=
avoids ufs_create() returning ERELOOKUP?=0A=
=0A=
rick=0A=
=0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968DC349AFD081480768028DDD70>