From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 19:41:45 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 E1BBE16A4CE; Wed, 27 Apr 2005 19:41:44 +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 j3RJfi3k040031; Wed, 27 Apr 2005 15:41:44 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3RJfiUm040030; Wed, 27 Apr 2005 15:41:44 -0400 (EDT) (envelope-from green) Date: Wed, 27 Apr 2005 15:41:44 -0400 From: Brian Fundakowski Feldman To: Marc Olzheim Message-ID: <20050427194144.GC39270@green.homeunix.org> References: <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> <20050427190627.GB39270@green.homeunix.org> <20050427191938.GE6256@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050427191938.GE6256@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:41:45 -0000 On Wed, Apr 27, 2005 at 09:19:38PM +0200, Marc Olzheim wrote: > On Wed, Apr 27, 2005 at 03:06:27PM -0400, Brian Fundakowski Feldman wrote: > > > 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. > > Well, I took on that challenge and although it seems that the machine > completely hangs itself up for a while, it snaps out of it after it is > done. > > tehethereal tells me it is NFSv3, and the commits increase: > [....] Alright, thanks for testing. So the same bug exists in 4.x but may not actually deadlock the buffer cache in the same circumstances. If you feel like playing with it anymore, I would expect a certain write block size, maximum nfsiod, and total file size being written wouldn't be too hard to find that would deadlock 4.x, too. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\