Date: Tue, 14 Apr 2020 16:55:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 245619] BROKEN NFS SERVER OR MIDDLEWARE after resume Message-ID: <bug-245619-227-nfzHk4bd3O@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-245619-227@https.bugs.freebsd.org/bugzilla/> References: <bug-245619-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245619 --- Comment #1 from Conrad Meyer <cem@freebsd.org> --- The message indicates you got a GETATTR response for a file you didn't requ= est. In this case the NFS request was for "inode" 0x4, but you got back a GETATTR response for 0x2. There are some NFS WAN caching proxy devices that have a GETATTR cache, which is fine, but a bug produced corrupt responses. Without the loud warning, it is very confusing when your NFS client mount is random= ly corrupt. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245619-227-nfzHk4bd3O>