Date: Fri, 11 Dec 2020 20:46:51 -0500 From: J David <j.david.lists@gmail.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: Major issues with nfsv4 Message-ID: <CABXB=RSSE=yOwgOXsnbEYPqiWk5K5NfzLY=D%2BN9mXdVn%2B--qLQ@mail.gmail.com> In-Reply-To: <YQXPR0101MB09680D155B6D685442B5E25EDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> References: <CABXB=RRB2nUk0pPDisBQPdicUA3ooHpg8QvBwjG_nFU4cHvCYw@mail.gmail.com> <YQXPR0101MB096849ADF24051F7479E565CDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <CABXB=RSyN%2Bo2yXcpmYw8sCSUUDhN-w28Vu9v_cCWa-2=pLZmHg@mail.gmail.com> <YQXPR0101MB09680D155B6D685442B5E25EDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 11, 2020 at 6:28 PM Rick Macklem <rmacklem@uoguelph.ca> wrote: > I am afraid I know nothing about nullfs and jails. I suspect it will be > something related to when file descriptors in the NFS client mount > get closed. What does NFSv4 do differently than NFSv3 that might upset a low-level consumer like nullfs? > Well, NFSv3 is not going away any time soon, so if you don't need > any of the additional features it offers... If we did not want the additional features, we definitely would not be attempting this. > a user would have to run their own custom hacked > userland NFS client. Although doable, I have never heard of it being done. Alex beat me to libnfs. What about this as a stopgap measure? > How explosive would adding SO_REUSEADDR to the NFS client be? It's > not a full solution, but it would handle the TIME_WAIT side of the > issue. The kernel NFS networking code is confusing to me. I can't even figure out where/how NFSv4 binds a client socket to know if it's possible. (Pretty sure the code in sys/nfs/krpc_subr.c is not it.) Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABXB=RSSE=yOwgOXsnbEYPqiWk5K5NfzLY=D%2BN9mXdVn%2B--qLQ>