From owner-freebsd-current Thu Jan 21 21:41:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21035 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:41:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21029 for ; Thu, 21 Jan 1999 21:41:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA47389; Thu, 21 Jan 1999 20:39:21 -0800 (PST) (envelope-from dillon) Date: Thu, 21 Jan 1999 20:39:21 -0800 (PST) From: Matthew Dillon Message-Id: <199901220439.UAA47389@apollo.backplane.com> To: "D. Rock" Cc: current@FreeBSD.ORG Subject: Re: NFS v3 issue References: <36A711FD.85F65545@cs.uni-sb.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :With NFS v3 there seem still to be some open issues. :Im running the latest (4.0)-current with the new vm/NFS changes. :While I haven't found any problems with NFSv2 so far, v3 still seems to make :trouble. : :I noticed the error some months ago, while my /usr/obj was NFS mounted, and :a build failed while making termcap.db. Today, I gave it another try. :I copied /usr/src/share/termcap into an NFS mounted directory and did :a "make". I compared the output of termcap.db with the one build on the local :drive. :While the NFS mounted one was only 1077760 bytes in size, the correct :size (from the local build) should be 1245184 bytes. I did the build :several times, everytime I got the same values. I then remounted the :direcory NFSv2. Now the build produced the right file (in size and content). : :The NFS Server is a Solaris 7 machine. : :Can anyone else confirm this error? : :Daniel I can't help you here, but I want to make sure: The problems you are having are the same problems you were having a few months ago? ( I want to make sure I haven't introduced new problems in -4.x, and if I have to fix them ASAP! ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message