From owner-freebsd-questions@FreeBSD.ORG Fri Feb 13 02:22:21 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB85416A4CE for ; Fri, 13 Feb 2004 02:22:21 -0800 (PST) Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.8.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65CAD43D1D for ; Fri, 13 Feb 2004 02:22:21 -0800 (PST) (envelope-from kheuer2@gwdg.de) Received: from gwdu60.gwdg.de (localhost [127.0.0.1]) by gwdu60.gwdg.de (8.12.9p2/8.12.8) with ESMTP id i1DALrG3096058; Fri, 13 Feb 2004 11:21:53 +0100 (CET) (envelope-from kheuer2@gwdg.de) Received: from localhost (kheuer2@localhost)i1DALhvY096053; Fri, 13 Feb 2004 11:21:53 +0100 (CET) X-Authentication-Warning: gwdu60.gwdg.de: kheuer2 owned process doing -bs Date: Fri, 13 Feb 2004 11:21:43 +0100 (CET) From: Konrad Heuer To: "Loren M. Lang" In-Reply-To: <20040213092856.GB2387@alzatex.com> Message-ID: <20040213111325.M94859@gwdu60.gwdg.de> References: <20040213092856.GB2387@alzatex.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD Mailing list Subject: Re: FreeBSD Locked Up X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 10:22:22 -0000 On Fri, 13 Feb 2004, Loren M. Lang wrote: > I have been using FreeBSD 4.9 on a Compaq Presario laptop for about 3 > 1/2 months now without any troubles, and before that RedHat Linux for > about a year and a half. Just yesterday morning though I awoke to find > my system completely frozen, no screensaver was on, but I couldn't move > the mouse pointer, switch vcs, or ssh in, though, strangely enough I > could ping it. Is there anything I can do now to try and figure out why > it might of crashed or is there any possible cause? I notice such phenomena from time to time, too. I don't know why it happens, maybe because of insufficient kernel resources or driver problems or hardware failures. ping is still possible in most of these cases since response happens on a relative low level. > Also, on reboot, I notice fsck took a considerable time to check the > disk, though nothing major was found that interrupted the boot process. > Is this because FreeBSD doesn't use a journalling filesystem? I think I > read somewhere that FreeBSD chose to use a filesystem with soft updates > over a journalling one because it provides relatively equal data integrity > compared to a journalling one, but is more efficient with the order of > writing data, but does this mean that FreeBSD will always take longer to > recover from a crash? Beginning with FreeBSD 5.0, it is possible to mount a filesystem immediatly even if it is dirty, caused by a crash. The file system check will be delayed for some time till the system is running. That's possible because soft updates also help to minimize the relevancy of inconsistencies. In FreeBSD 4.9 and earlier, a filesystem check is inevitable if the file system is dirty. Konrad Heuer (kheuer2@gwdg.de) ____ ___ _______ GWDG / __/______ ___ / _ )/ __/ _ \ Am Fassberg / _// __/ -_) -_) _ |\ \/ // / 37077 Goettingen /_/ /_/ \__/\__/____/___/____/ Germany