From owner-freebsd-current@FreeBSD.ORG Tue Jun 20 22:31:16 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE42316A47C for ; Tue, 20 Jun 2006 22:31:16 +0000 (UTC) (envelope-from mohan_srinivasan@yahoo.com) Received: from web30803.mail.mud.yahoo.com (web30803.mail.mud.yahoo.com [68.142.200.146]) by mx1.FreeBSD.org (Postfix) with SMTP id 0955843D46 for ; Tue, 20 Jun 2006 22:31:15 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Received: (qmail 21445 invoked by uid 60001); 20 Jun 2006 22:31:15 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=cz9zfw8LqJFUOwmJKWQKwZ++xOEr+RoRjZAim7N0uzzV/VHcyjpjCkOVgk3ijBx5bxbN+3SjsC9tlbqfdlncTh7DFBmn9/TAiuzUsF2YRU+rCJ5StK6NYMFIvTkG9QU5qh/L5SkxQWiGxqFiiEqkLzALmVs7dkJ3Ln0yGvNyd40= ; Message-ID: <20060620223115.21443.qmail@web30803.mail.mud.yahoo.com> Received: from [207.126.239.39] by web30803.mail.mud.yahoo.com via HTTP; Tue, 20 Jun 2006 15:31:15 PDT Date: Tue, 20 Jun 2006 15:31:15 -0700 (PDT) From: Mohan Srinivasan To: "Matthew D. Fuller" , obrien@freebsd.org, Robert Watson , freebsd-current@freebsd.org In-Reply-To: <20060620205617.GR83482@over-yonder.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Often experiencing nfs server foo:/bar: not responding X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2006 22:31:17 -0000 Hi, I am not able to reproduce the problems you report :( 1) On the latest -current NFS client, and against both NetApp filers and FreeBSD 4.11 servers, mounting NFS/UDP, I copied a .tgz image of the freebsd source tree to an NFS mount, untarred it over NFS and built the kernel over NFS. That works fine. I don't see any "server not responding messages". 2) Then I did the same with a FreeBSD4.11 client and the FreeBSD -current server - copying the .tgz file over NFS and untarring it over NFS, to see if might be a -current NFS server issue. That works fine too. Unfortunately, I am unable to mount -current against -current here. I have a mix of bge and fxp cards. mohan --- "Matthew D. Fuller" wrote: > On Tue, Jun 20, 2006 at 01:45:07PM -0700 I heard the voice of > David O'Brien, and lo! it spake thus: > > > > Note that mounting NFS /home with -T "fixes" the problem. > > Hm, that's a point. I have an early-June -CURRENT as a NFS client on > a late-Nov. -CURRENT NFS server, and haven't had any troubles. But I > do use TCP mounts. > > > -- > Matthew Fuller (MF4839) | fullermd@over-yonder.net > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >