From owner-freebsd-stable@FreeBSD.ORG Thu Sep 4 18:39:51 2003 Return-Path: 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 53AF116A4BF for ; Thu, 4 Sep 2003 18:39:51 -0700 (PDT) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22EB143FDF for ; Thu, 4 Sep 2003 18:39:50 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.9/8.12.9) with ESMTP id h851dlG7014877; Thu, 4 Sep 2003 18:39:47 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.9/8.12.9/Submit) id h851dlxE014876; Thu, 4 Sep 2003 18:39:47 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Thu, 4 Sep 2003 18:39:47 -0700 From: David Schultz To: Kevin Bockman Message-ID: <20030905013947.GA14776@HAL9000.homeunix.com> Mail-Followup-To: Kevin Bockman , freebsd-stable@freebsd.org References: <20030831173259.35921.qmail@web41809.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030831173259.35921.qmail@web41809.mail.yahoo.com> cc: freebsd-stable@FreeBSD.ORG Subject: Re: Filesystem problem 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: Fri, 05 Sep 2003 01:39:51 -0000 On Sun, Aug 31, 2003, Kevin Bockman wrote: > Running 5.1 is a different story. I did a low level > format of the drive then I did a clean > install of 5.1-RELEASE and cvsup'd to -p2. Every time > I do this, it's great for a day or so then it acts up. > Before after it started, even if I rebooted it would > immediately start up. On 5.1, it is only hanging for > that process and everything else is fine. I can still > login, webserver responds, etc. [...] > Any ideas on what else to check or other helpful hints > would help bunches. The output of 'ps axl' might help track down exactly where in the kernel the affected processes are getting stuck. BTW, I think 5.X issues are still discussed on current@ for the most part, at least until 6.X is forked.