Date: Thu, 10 Dec 2020 15:30:42 -0500 From: J David <j.david.lists@gmail.com> To: Peter Eriksson <pen@lysator.liu.se> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: Major issues with nfsv4 Message-ID: <CABXB=RShn6UovK%2B0TH1dmwY%2BbpUKV1wgYvJa9ATSm9uscCopVw@mail.gmail.com> In-Reply-To: <976EC1BD-AB37-478C-B567-E8013E80F071@lysator.liu.se> References: <CABXB=RRB2nUk0pPDisBQPdicUA3ooHpg8QvBwjG_nFU4cHvCYw@mail.gmail.com> <976EC1BD-AB37-478C-B567-E8013E80F071@lysator.liu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Ah, oops. The "12.2 servers" referred to at the top of the message are the NFS *clients* in this scenario. They are application servers, not NFS servers. Sorry for the confusing overloaded usage of "server" there! Everything in the message (dmesg, tcpdump, nfsstat, etc.) is from the perspective of a FreeBSD 12.2 NFS client, which is where the problems are occurring. Our Linux servers (machines? instances? hosts? nodes?) that are NFS clients have been running NFSv4 against the same servers for many years without incident. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABXB=RShn6UovK%2B0TH1dmwY%2BbpUKV1wgYvJa9ATSm9uscCopVw>