From owner-freebsd-hackers Wed Jan 10 01:41:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA26259 for hackers-outgoing; Wed, 10 Jan 1996 01:41:45 -0800 (PST) Received: from mail.fwi.uva.nl (root@mail.fwi.uva.nl [146.50.4.20]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA26249 for ; Wed, 10 Jan 1996 01:41:27 -0800 (PST) From: frank@fwi.uva.nl Received: from atlas.fwi.uva.nl by mail.fwi.uva.nl with ESMTP (sendmail 8.6.12/config 5.15). id KAA00951; Wed, 10 Jan 1996 10:41:23 +0100 Received: from localhost by atlas.fwi.uva.nl (sendmail 8.6.12/config 5.12). id KAA18577; Wed, 10 Jan 1996 10:41:20 +0100 Message-Id: <199601100941.KAA18577@atlas.fwi.uva.nl> Date: Wed, 10 Jan 1996 10:41:20 +0100 X-Organisation: Faculty of Mathematics, Computer Science, Physics & Astronomy University of Amsterdam Kruislaan 403 NL-1098 SJ Amsterdam The Netherlands X-Phone: +31 20 525 7463 X-Fax: +31 20 525 7490 To: freebsd-hackers@freebsd.org Subject: NFS3 query Sender: owner-hackers@freebsd.org Precedence: bulk [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, - Frank