From owner-freebsd-current  Wed Dec 15 11:56:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 16D0615590
	for <freebsd-current@FreeBSD.ORG>; Wed, 15 Dec 1999 11:56:45 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA03966;
	Wed, 15 Dec 1999 14:56:44 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA19203;
	Wed, 15 Dec 1999 14:56:13 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 15 Dec 1999 14:56:13 -0500 (EST)
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Serious server-side NFS problem
In-Reply-To: <199912151739.JAA32687@apollo.backplane.com>
References: <14423.46117.353932.473968@grasshopper.cs.duke.edu>
	<199912151711.JAA32205@apollo.backplane.com>
	<14423.52876.91488.48428@grasshopper.cs.duke.edu>
	<199912151739.JAA32687@apollo.backplane.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14423.60766.907301.965548@grasshopper.cs.duke.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Matthew Dillon writes:
 > 
 > :
 > :
 > :Matthew Dillon writes:
 > : >     This is very odd.  Does it lockup with UDP or only with TCP?   And only
 > : >     with a solaris client?
 > :
 > :This appears to be solaris only.  I just tried a UDP mount & I see the
 > :same problem.   Is there anything else I can do?
 > 
 >     Yes, see if you can repeat the problem with a shorter dd count -- see
 >     how small a count you can achieve and still produce the problem, then
 >     do a nice long protocol trace.
 > 
 > 						-Matt

I've tried.  I can get the file to take a hell of a long time to close
with a count as short as 512 64k chunks.  But it eventually completes.
Perhaps the large files would eventually complete too, if I were
patient enough..

I've left you a full trace on freefall in ~gallatin of a 384MB test
(client has 320MB, server has 384MB).

large.gz :	 trace from file creation to server reboot  Server is
		 running kernel from today.

large_reboot.gz: trace after server is rebooted into ~July kernel
		 and the writes complete.

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message