From owner-freebsd-stable@FreeBSD.ORG Wed Jul 19 14:23:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E18E16A4DF; Wed, 19 Jul 2006 14:23:18 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FD9C43D5C; Wed, 19 Jul 2006 14:23:17 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 0B2E0291B0B; Wed, 19 Jul 2006 11:23:11 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 69607-08; Wed, 19 Jul 2006 14:23:17 +0000 (UTC) Received: from ganymede.hub.org (blk-224-179-167.eastlink.ca [24.224.179.167]) by hub.org (Postfix) with ESMTP id 83BE2291B0A; Wed, 19 Jul 2006 11:23:10 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 0D8D95D15B; Wed, 19 Jul 2006 11:23:22 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 0700C4AAD1; Wed, 19 Jul 2006 11:23:22 -0300 (ADT) Date: Wed, 19 Jul 2006 11:23:21 -0300 (ADT) From: User Freebsd To: Robert Watson In-Reply-To: <20060719151327.H5132@fledge.watson.org> Message-ID: <20060719112208.Y1799@ganymede.hub.org> References: <20060705100403.Y80381@fledge.watson.org> <20060705234514.I70011@fledge.watson.org> <20060715000351.U1799@ganymede.hub.org> <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> <20060718074804.W1799@ganymede.hub.org> <20060719112424.GK1464@deviant.kiev.zoral.com.ua> <20060719082627.H1799@ganymede.hub.org> <20060719151327.H5132@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: file system deadlock - the whole story? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jul 2006 14:23:18 -0000 On Wed, 19 Jul 2006, Robert Watson wrote: > > On Wed, 19 Jul 2006, User Freebsd wrote: > >> Also note that under FreeBSD 4.x, all three of these machines were pretty >> much my more solid machines, with even more vServers running on them then >> I'm able to run with 6.x ... once I got rid of using unionfs, stability >> skyrocketed :( >> >> Hrmmmm ... but, your 'controller driver' comment ... that is one common >> thing amongst all three servers ... they are all running the iir driver ... >> not sure the *exact* controller, but pluto (older Dual-PIII) shows it as: > > Yes, this was going to be my next question -- if you're seeing wedges under > load and there's a common controller in use, maybe we're looking at a driver > bug. Bugs of those sort typically look a lot like what you describe: an I/O > is "lost" and so eveything that depends on the I/O wedges waiting for it, > leading to a lot of processes hanging around waiting for vnode locks, etc. 'k, but how do we debug *that*? :( If it was one, I'd suspect hardware ... but *three*, and only acting up *after* upgrading to FreeBSD 6.x, and only acting up under load ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664