From owner-freebsd-stable@FreeBSD.ORG Fri Jul 29 08:24:07 2005 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 289C516A41F for ; Fri, 29 Jul 2005 08:24:07 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id D38DD43D45 for ; Fri, 29 Jul 2005 08:24:06 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 82DB046B03; Fri, 29 Jul 2005 04:24:06 -0400 (EDT) Date: Fri, 29 Jul 2005 09:25:42 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20050728231728.E968@ganymede.hub.org> Message-ID: <20050729092127.V74149@fledge.watson.org> References: <20050728231728.E968@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Consistent file system hang with RELENG_6 of today ... 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: Fri, 29 Jul 2005 08:24:07 -0000 On Thu, 28 Jul 2005, Marc G. Fournier wrote: > 'k, I'm starting to play with 6.x, for our new server ... my priority > right now is to just have it run the existing 'jail' environments from > my 4.x machine, while I work on getting all of our servers up to 6.x, > and then will worry about the jail's themselves ... > > When I try and startup the 4.x jail on my 6.x machine, it "hangs" the > file system that the jail directory hierarchy happens to be mounted on > though ... twice in a row so far ... > > Now, I'm suspecting (and am going to try without it) that it might be > because I'm mounting devfs within the 4.x jail, but even then, it > shouldn't hang things up, only generate a whack of errors ... > > I have a good dump (CTL-ALT-ESC -> panic), but do not have a clue what > to offer from within there that might be of any use ... > > If anyone is interested ... ? If you can get into DDB and have serial console output, the following would be useful: The output of 'show pcpu' The output of 'show pcpu X' for each present cpu, starting with 0. The output of 'ps' The output of 'trace' for the currently running thread, and each non-idle thread shown in the show pcpu output The output of 'show lockedvnods' It would also be useful if, relating to the startup of the jail, you can identify the point in the jail boot where it wedges, and if you hit Ctrl-T, what process is shown as running and what state it is in, and using DDB, trace that process. If you could show the trace output for each process listed in "show lockevnods". Likely, there is a leaked lock or a low buffer condition. However, once we have the above output we should be able to say more. The above will hopefully tell us whether it's a vnode deadlock, and ideally, the approximate source. Robert N M Watson