From owner-freebsd-stable Tue Jun 8 13:16: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 145081522F; Tue, 8 Jun 1999 13:15:59 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id NAA03998; Tue, 8 Jun 1999 13:15:54 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 8 Jun 1999 13:15:53 -0700 (PDT) From: Doug White To: michael@alderete.com Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, alderete@be.com Subject: Re: [HELP!] Crashing FreeBSD server with file system corruption In-Reply-To: <19990605175807.21420.rocketmail@web126.yahoomail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Jun 1999, Michael A. Alderete wrote: > I have a FreeBSD-based web/ftp server that is crashing > regularly, and the crashes are causing (caused by)file > system corruption. When reporting "crashes", if you get a kernel panic, AT MINUMUM you *must* include the panic output. If you can reproduce it, you should build a debugging kernel, turn dumps on, cause a panic, and trace back the dump. This points the finger at the offending function. The Handbook section on kernel debugging is highly recommended. For fun, I'd try using a singleprocessor kernel and see if it helps; I doubt it will, but it's a good idea to eliminate possibilities. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message