From owner-freebsd-current Mon Nov 25 7:24:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF94737B406 for ; Mon, 25 Nov 2002 07:24:57 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 670F143E4A for ; Mon, 25 Nov 2002 07:24:57 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gAPFOlBF034051; Mon, 25 Nov 2002 10:24:47 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 25 Nov 2002 10:24:46 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Mikhail Teterin Cc: current@FreeBSD.org Subject: Re: -current unusable after a crash In-Reply-To: <200211250959.39594.mi+mx@aldan.algebra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Nov 2002, Mikhail Teterin wrote: > The only way to get my -current system back to normal after a crash is > to boot into single user and do an explicit ``fsck -p''. > > Otherwise the system will, seemingly, boot fine, but none of the ttyvs > will accept any input, although tty-switching works fine. Remote > connections (ssh, telnet) don't bring up the login prompt. > > I thought, this might be due to the priority of the background fsck and > have once left it alone for several hours -- with no effect. The usual > fsck takes a few minutes. > > There are three drives in the system -- a 4G SCSI (on ahc0) with /, > /usr, /opt, and /home on it, and two 30Gb IDEs coupled into one big ccd. Any chance we can get you to break into ddb on the console, do a ps, and see what the processes are waiting for? Also, if they're waiting on something like "ufs" or "inode", generated ddb traces of the processes would be interesting. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message