Date: Mon, 25 Nov 2002 10:24:46 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: Mikhail Teterin <mi+mx@aldan.algebra.com> Cc: current@FreeBSD.org Subject: Re: -current unusable after a crash Message-ID: <Pine.NEB.3.96L.1021125102358.33619A-100000@fledge.watson.org> In-Reply-To: <200211250959.39594.mi%2Bmx@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1021125102358.33619A-100000>