Date: Thu, 24 Oct 2002 08:23:31 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Andreas Ntaflos <ant@overclockers.at> Cc: Kris Kennaway <kris@obsecurity.org>, freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: fsck lasting several hours (and then forever) after crash Message-ID: <20021024152331.GA43887@xor.obsecurity.org> In-Reply-To: <20021024150545.GA243@Deadcell.ant> References: <20021024141508.GB309@Deadcell.ant> <20021024144322.GB42385@xor.obsecurity.org> <20021024150545.GA243@Deadcell.ant>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Oct 24, 2002 at 05:05:45PM +0200, Andreas Ntaflos wrote: > > What happens when you press ^T? > > 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? Also, what version are you running? Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9uBByWry0BWjoQKURAmaYAKCWfP+WsNU5U2KrlcW5UK5UmUC7agCgtSK9 ujhalX4J67Del7IV0mX7Qks= =MeSG -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021024152331.GA43887>