From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 19:06:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 29EBF16A4CE; Wed, 27 Apr 2005 19:06:28 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3RJ6RT0039873; Wed, 27 Apr 2005 15:06:27 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3RJ6RZl039872; Wed, 27 Apr 2005 15:06:27 -0400 (EDT) (envelope-from green) Date: Wed, 27 Apr 2005 15:06:27 -0400 From: Brian Fundakowski Feldman To: Marc Olzheim Message-ID: <20050427190627.GB39270@green.homeunix.org> References: <20050426155043.GC5789@green.homeunix.org> <20050426160609.GA68511@stack.nl> <20050426162549.GD5789@green.homeunix.org> <20050426164346.GA68763@stack.nl> <20050426193602.GE5789@green.homeunix.org> <20050427081746.GA66441@stack.nl> <20050427160857.GF5789@green.homeunix.org> <20050427171523.GB5984@stack.nl> <20050427183435.GA39270@green.homeunix.org> <20050427184203.GD6256@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050427184203.GD6256@stack.nl> User-Agent: Mutt/1.5.6i cc: freebsd-stable@freebsd.org Subject: Re: NFS client/buffer cache deadlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2005 19:06:28 -0000 On Wed, Apr 27, 2005 at 08:42:03PM +0200, Marc Olzheim wrote: > On Wed, Apr 27, 2005 at 02:34:35PM -0400, Brian Fundakowski Feldman wrote: > > Alright, thanks for helping with this :-) Do you think you can find > > a way to tell if in 4.x you're actually using NFSv3/transactions? I > > would really like to know why 4.x isn't deadlocking, and that's the > > most plausible explanation I can think of right now. > > > > The behavior could also be totally different due to nfsiod, lack thereof, > > or its settings. Are you running nfsiod on 4.x, and if so, how many? > > On 5.x+ the default maximum of nfsiods is 20. > > The install I ran the speedtest on is: > > FreeBSD baroque.ilse.net 4.10-STABLE FreeBSD 4.10-STABLE #23: Wed Aug 4 15:18:52 CEST 2004 root@tango.ilse.net:/usr/obj/usr/src/sys/BAROQUE i386 > > and runs 6 nfsiods. > > How can I tell whether it uses transactions ? I am not sure -- it should with NFSv3 though. Does "mount -v" tell you anything more detailed? I suppose that nfsstat may also be used -- the "commit" count should only increase when it does an NFSv3 commit operation. > The NFS server is mounted with: > > mount_nfs -c -P -a 0 -r 8192 -w 8192 -i -o rw,noatime,nointr host:/path /nfs/host/path So the only really visible difference is 6 nfsiod versus 20 nfsiod. I think if you increased the nfsiod on that 4.x box to something much higher it would deadlock the same, then, assuming that all else is equal. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\