Date: Thu, 24 Oct 2002 18:12:27 +0200 From: Andreas Ntaflos <ant@overclockers.at> To: Kris Kennaway <kris@obsecurity.org> 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> In-Reply-To: <20021024152331.GA43887@xor.obsecurity.org> References: <20021024141508.GB309@Deadcell.ant> <20021024144322.GB42385@xor.obsecurity.org> <20021024150545.GA243@Deadcell.ant> <20021024152331.GA43887@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021024161227.GA248>