From owner-freebsd-hackers Wed Jan 10 05:09:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA05512 for hackers-outgoing; Wed, 10 Jan 1996 05:09:39 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA05507 for ; Wed, 10 Jan 1996 05:09:36 -0800 (PST) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id FAA02797 for ; Wed, 10 Jan 1996 05:08:52 -0800 Received: (from dfr@localhost) by minnow.render.com (8.6.12/8.6.9) id NAA29285; Wed, 10 Jan 1996 13:05:48 GMT Date: Wed, 10 Jan 1996 13:05:47 +0000 (GMT) From: Doug Rabson To: frank@fwi.uva.nl cc: freebsd-hackers@freebsd.org Subject: Re: NFS3 query In-Reply-To: <199601100941.KAA18577@atlas.fwi.uva.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk On Wed, 10 Jan 1996 frank@fwi.uva.nl wrote: > > [I'm not on this list, so please Cc any replies to me..] > > I've been integrating Rick Macklem's NFSv3 code (from Lite2) into > NetBSD-current. After passing through several tests in several configurations, > I thought I was mostly done with it. However, I decided to scan the > FreeBSD mailing lists for any problems that you folks might have had > integrating it, since you have done that already a while ago. > > I noticed a message from Bruce Evans, dated August 2nd I think, in which > he wrote: > > > 3. Making of vnode_if.[ch] for the kernel on the client with /usr NFSv3- > > mounted gives corrupted files (with small pieces missing or something like > > that). > > So I tried it and, sure enough, it failed. It only happens when v3 is used, > without NQNFS extensions. It seems that the last buffer of the files is not > written to the server, creating truncated files. > > It isn't one of the 2 bugs reported in the patches that Rick put up for ftp, > I checked that. > > My question is: did you guys already fix this one (I guess so, since it > was reported 4 months ago), and how did you fix it? > > I just thought I'd ask before going off and hunting it down myself, there's > no to reinvent the wheel after all. > > Thanks a lot in advance, Wasn't it something to do with buf->b_validoff and buf->b_validend not being fully supported (at the time) by the VM system? I can't remember if it was fixed at the time. Is anyone using NFSv3 in current at the moment? -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939