From owner-freebsd-current@FreeBSD.ORG Wed Aug 27 06:07:07 2003 Return-Path: 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 00E3816A4BF for ; Wed, 27 Aug 2003 06:07:07 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A2D243FF3 for ; Wed, 27 Aug 2003 06:07:05 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h7RD6frO024030; Wed, 27 Aug 2003 09:06:41 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h7RD6fwl024027; Wed, 27 Aug 2003 09:06:41 -0400 (EDT) Date: Wed, 27 Aug 2003 09:06:41 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Pawel Worach In-Reply-To: <3F4BEA15.3030104@telia.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alexander Leidinger cc: freebsd-current@freebsd.org Subject: Re: nfs tranfers hang in state getblck or nfsread X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 27 Aug 2003 13:07:07 -0000 On Wed, 27 Aug 2003, Pawel Worach wrote: > >In this configuration I see a lot of "nfs server ...: is not responding" > >and "nfs server ...: is alive again" when I copy large files (e.g. a CD > >image). All of them happen in the same second. I haven't looked at the > >state or priority of the cp process when this happens. > > I have seen this too and i can reproduce it. I have a diskless client > and if i unplug the power and boot it up again i see the "nfs server not > responding" messages for every filesystem being mounted. Both client and > server are of course FreeBSD-current, i have seen this for about four > mounts now. I have a very similar configuration, but it sounds like I'm not bumping into the same problem. Are you using NFSv2 or v3, and how many file systems are you mounting? Are you generally using UFS1 or UFS2? Right now, I'm mounting a single UFS2 file system was the root, and I believe right now we always mount NFS roots at NFSv2, which could by why I'm not seeing the same problem... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories