From owner-freebsd-stable Thu Oct 24 9:12:45 2002 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 612B637B401; Thu, 24 Oct 2002 09:12:42 -0700 (PDT) Received: from viefep14-int.chello.at (viefep14-int.chello.at [213.46.255.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CA4643E3B; Thu, 24 Oct 2002 09:12:40 -0700 (PDT) (envelope-from ant@overclockers.at) Received: from Deadcell.ant ([212.17.108.240]) by viefep14-int.chello.at (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20021024161233.WBRS29435.viefep14-int.chello.at@Deadcell.ant>; Thu, 24 Oct 2002 18:12:33 +0200 Received: from Deadcell.ant (localhost [127.0.0.1]) by Deadcell.ant (8.12.6/8.12.6) with ESMTP id g9OGCXYv000326; Thu, 24 Oct 2002 18:12:33 +0200 (CEST) (envelope-from ant@Deadcell.ant) Received: (from ant@localhost) by Deadcell.ant (8.12.6/8.12.6/Submit) id g9OGCSQA000325; Thu, 24 Oct 2002 18:12:28 +0200 (CEST) Date: Thu, 24 Oct 2002 18:12:27 +0200 From: Andreas Ntaflos To: Kris Kennaway Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: fsck lasting several hours (and then forever) after crash Message-ID: <20021024161227.GA248@Deadcell.ant> References: <20021024141508.GB309@Deadcell.ant> <20021024144322.GB42385@xor.obsecurity.org> <20021024150545.GA243@Deadcell.ant> <20021024152331.GA43887@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021024152331.GA43887@xor.obsecurity.org> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.7-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Oct 24, 2002 at 08:23:31AM -0700, Kris Kennaway wrote: > > > > Well, nothing. Just nothing. The num-lock key works (the LED goes on and off), > > so the keyboard itself is not dead. But fsck does not let me get out. Brrrr. > > > > Could this be serious? Either for my disk which might be about to go to hell, > > or for fsck? > > Could be an obscure bug in fsck. If you check on another console (or > suspend fsck and run it in the background, if running single-user) is > it still using CPU? I don't know since I can't even change to another console, nor can I suspend fsck to the background. I also think that the machine itself is not accessible via network (ping, ssh) anymore, and not responding to any keyboard-input. > Also, what version are you running? The version coming with FreeBSD 4.7-STABLE as of Oct 10. Hope this helps... Is there anything else I could do to help solving this problem? regards -- Andreas "ant" Ntaflos | "A cynic is a man who knows the price of ant@overclockers.at | everything, and the value of nothing." Vienna, AUSTRIA | Oscar Wilde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message