Date: Tue, 8 Jun 1999 13:15:53 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> 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 Message-ID: <Pine.BSF.4.03.9906081309200.29439-100000@resnet.uoregon.edu> In-Reply-To: <19990605175807.21420.rocketmail@web126.yahoomail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9906081309200.29439-100000>