From gallatin@wind.cs.duke.edu  Wed Jul  2 06:35:24 1997
Received: from wind.cs.duke.edu ([152.3.145.51])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04017
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 2 Jul 1997 06:35:23 -0700 (PDT)
Received: (from gallatin@localhost)
	by wind.cs.duke.edu (8.8.5/8.8.5) id JAA01366;
	Wed, 2 Jul 1997 09:35:07 -0400 (EDT)
Message-Id: <199707021335.JAA01366@wind.cs.duke.edu>
Date: Wed, 2 Jul 1997 09:35:07 -0400 (EDT)
From: Andrew Gallatin <gallatin@wind.cs.duke.edu>
Reply-To: gallatin@wind.cs.duke.edu
To: FreeBSD-gnats-submit@freebsd.org
Subject: 2.2-RELEASE/Digital UNIX NFSv3 0 length files
X-Send-Pr-Version: 3.2

>Number:         4012
>Category:       kern
>Synopsis:       [nfs] 2.2-RELEASE/Digital UNIX NFSv3 0 length files
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul  2 06:40:03 PDT 1997
>Closed-Date:    Fri Dec 29 20:25:10 GMT 2006
>Last-Modified:  Fri Dec 29 20:25:10 GMT 2006
>Originator:     Andrew Gallatin
>Release:        FreeBSD 2.2.2-RELEASE i386
>Organization:
Duke University, Dept. of Computer Science
>Environment:
FreeBSD wind.cs.duke.edu 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #2: Tue Jun  3 10:30:58 EDT 1997     gallatin@wind.cs.duke.edu:/usr/project/ari1/users/gallatin/freebsd/sys/compile/WINDPROF  i386
200Mhz P6, 256k cache, 128MB RAM, Asus P/I-XP6NP5 motherbd.
20 nfsiods
NFS mount was over a switched, full-duplex 100Mb/sec link.
No special NFS options were used (other than V3 vs V2).
	

>Description:
When building a kernel in a filesystem mounted via NFS from a DEC
Alphaserver 2000 running Digital UNIX 3.2g, some (about 10%) object
files are 0 length.  This occurs only when the filesystem is mounted
via NFSv3.  The mount was via UDP (TCP was not tested, as DU 3.2G
doesn't support NFS over TCP).  Falling back to NFSv2 cures the
problem.

NFS mounts to a different machine running Digital UNIX 4.0 were
briefly tested, and do not appear to exhibit the problem.  This made
me suspect a bug in Digital UNIX 3.2g.  DEC tech.  support was
contacted, but no relevant patches were found by them.  They suggested
I patch the DU kernel & change the 'kudp_usedrc' from 1 to 0 (this
apparently controls some nfs server request cache).  This had no
effect.  I also tried turning off nfs3_write_gather in the DU kernel,
again w/no effect.

>How-To-Repeat:
Mount a filesystem via NFSv3 from a machine running Digital UNIX
3.2g (3.2{c-f} will probably also exhibit this behavior).  Attempt to
build a large program (like the FreeBSD kernel).  Observe that about
10% of the object files are 0 length.

	

>Fix:
One can work around this problem by using only NFSv2 mounts
when interoperating w/a Digital UNIX 3.2g machine.

	

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: max 
Responsible-Changed-When: Wed Jul 2 22:43:03 PDT 1997 
Responsible-Changed-Why:  
Misfiled PR. 
Responsible-Changed-From-To: freebsd-bugs->peter 
Responsible-Changed-By: peter 
Responsible-Changed-When: Sun Apr 26 01:14:29 PDT 1998 
Responsible-Changed-Why:  
I'll look into this.. 
Responsible-Changed-From-To: peter->freebsd-bugs 
Responsible-Changed-By: peter 
Responsible-Changed-When: Mon Mar 29 11:14:12 PST 2004 
Responsible-Changed-Why:  
Return neglected PR to the pool 

http://www.freebsd.org/cgi/query-pr.cgi?pr=4012 
State-Changed-From-To: open->closed 
State-Changed-By: remko 
State-Changed-When: Fri Dec 29 20:25:03 UTC 2006 
State-Changed-Why:  
too much had changed, assuming this got fixed in the meantime, that 
said; digital unix is not commonly used anymore, at least not at the 
areas i work in. closing the PR, please contact me if i was wrong. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=4012 
>Unformatted:
