From owner-freebsd-hackers Thu Mar 14 1:13:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 8B8BE37B417 for ; Thu, 14 Mar 2002 01:13:07 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Mar 2002 09:13:06 +0000 (GMT) To: Daniel O'Connor Cc: freebsd-hackers@freebsd.org Subject: Re: Porting a userland NFS server In-Reply-To: Your message of "14 Mar 2002 18:18:12 +1130." <1016088492.522.30.camel@chowder.gsoft.com.au> Date: Thu, 14 Mar 2002 09:13:05 +0000 From: Ian Dowse Message-ID: <200203140913.aa48122@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <1016088492.522.30.camel@chowder.gsoft.com.au>, Daniel O'Connor writ es: >I end up with EFBIG when trying to read the .katie-server-info file, but >if I create a file inside the view (eg echo "abc" >foo) then it can be >read with no problem, _but_ the dump of NFS traffic doesn't show a read >for that file. At a guess, the server is incorrectly reporting the maximum file size. You might be able to verify this by creating a file of the same size as .katie-server-info and checking if you get the same error. The bug in the server is likely to be in its "fsinfo" op function - see the FSINFO3resok definition in RFC1813 for how the fsinfo reply is supposed to be formed. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message